Merge branch 'master' of github.com:parcel-bundler/parcel-css

Author: devongovett

node/index.d.ts

@@ -359,7 +359,9 @@ export interface ImportDependency {
   /** The `supports()` query for the `@import` rule. */
   supports: string | null,
   /** The source location where the `@import` rule was found. */
-  loc: SourceLocation
+  loc: SourceLocation,
+  /** The placeholder that the import was replaced with. */
+  placeholder: string
 }
 
 export interface UrlDependency {

src/properties/grid.rs

@@ -163,12 +163,12 @@ pub enum TrackBreadth {
 #[cfg_attr(feature = "jsonschema", derive(schemars::JsonSchema))]
 pub struct TrackRepeat<'i> {
   /// The repeat count.
-  count: RepeatCount,
+  pub count: RepeatCount,
   /// The line names to repeat.
   #[cfg_attr(feature = "serde", serde(borrow))]
-  line_names: Vec<CustomIdentList<'i>>,
+  pub line_names: Vec<CustomIdentList<'i>>,
   /// The track sizes to repeat.
-  track_sizes: Vec<TrackSize>,
+  pub track_sizes: Vec<TrackSize>,
 }
 
 /// A [`<repeat-count>`](https://drafts.csswg.org/css-grid-2/#typedef-track-repeat) value,

website/pages/docs.md

@@ -174,6 +174,6 @@ By default, Lightning CSS is strict, and will error when parsing an invalid rule
 
 Lightning CSS supports generating source maps when compiling, minifying, and bundling your source code to make debugging easier. Use the `sourceMap` option to enable it when using the API, or the `--sourcemap` CLI flag.
 
-If the input CSS came from another compiler such as SASS or Less, you can also pass an input source map to Lightning CSS using the `inputSourceMap` API option. This will map compiled locations back to their location in the original source code.
+If the input CSS came from another compiler such as Sass or Less, you can also pass an input source map to Lightning CSS using the `inputSourceMap` API option. This will map compiled locations back to their location in the original source code.
 
 Finally, the `projectRoot` option can be used to make file paths in source maps relative to a root directory. This makes build stable between machines.

website/pages/transforms.md

@@ -31,7 +31,7 @@ let res = transform({
     Length(length) {
       return {
         unit: length.unit,
-        value: length * 2
+        value: length.value * 2
       }
     }
   }
@@ -123,7 +123,7 @@ let res = transform({
               type: 'length-percentage',
               value: { type: 'dimension', value: property.value[0].value }
             };
-            
+
             return [
               { property: 'width', value },
               { property: 'height', value }

website/pages/transpilation.md

@@ -425,7 +425,7 @@ Lightning CSS can also be configured to compile several draft specs that are not
 
 ### Nesting
 
-The [CSS Nesting](https://drafts.csswg.org/css-nesting/) draft spec enables style rules to be nested, with the selectors of the child rules extending the parent selector in some way. This is very commonly supported by CSS pre-processors like SASS, but with this spec, it will eventually be supported natively in browsers. Lightning CSS compiles this syntax to un-nested style rules that are supported in all browsers today.
+The [CSS Nesting](https://drafts.csswg.org/css-nesting/) draft spec enables style rules to be nested, with the selectors of the child rules extending the parent selector in some way. This is very commonly supported by CSS pre-processors like Sass, but with this spec, it will eventually be supported natively in browsers. Lightning CSS compiles this syntax to un-nested style rules that are supported in all browsers today.
 
 Because nesting is a draft, it is not enabled by default. To use it, enable the `nesting` option under `drafts` when calling the Lightning CSS API. When using the CLI, enable the `--nesting` flag.