Tim van der Lippe
6d109a9d45
This also adds Python-2.0 to the list of accepted licenses. Lastly, it fixes a bug where the package.json files were incorrectly reordered. For the `exports` of a particular package, the order that the entrypoints are defined in is crucial. Therefore, we should not alter the order of entrypoints and instead maintain the originally defined ordering. We can use an `OrderedDict` to ensure that Python always loads the JSON files in the same order. DISABLE_THIRD_PARTY_CHECK=NPM update R=jacktfranklin@chromium.org Bug: none Change-Id: I5a309782de6015edea6ba3b502aa0db1f008d973 Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2692909 Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org> Reviewed-by: Jack Franklin <jacktfranklin@chromium.org> Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
PostCSS SCSS Syntax 
This module does not compile SCSS. It simply parses mixins as custom at-rules & variables as properties, so that PostCSS plugins can then transform SCSS source code alongside CSS.
Install
npm --save install postcss-scss
or (if you use Yarn)
yarn add --dev postcss-scss
Usage
There are two ways to use this parser:
1. SCSS Transformations
The main use case of this plugin is to apply PostCSS transformations directly to SCSS source code.
For example, you can lint SCSS source with Stylelint and linter will automatically fix issues in the source.
// postcss.config.js
module.exports = {
syntax: 'postcss-scss',
plugins: {
…
}
}
2. Inline Comments for PostCSS
Also you can use this parser just to add // single-line comment
to your PostCSS project (without any Sass):
:root {
// Main theme color
--color: red;
}
Note that you don’t need a special stringifier to handle the output; the default one will automatically convert single line comments into block comments.
// postcss.config.js
module.exports = {
parser: 'postcss-scss',
plugins: {
…
}
}
If you want Sass behaviour with removing inline comments, you can use postcss-strip-inline-comments plugin.