SUIT CSS preprocessor.
Provides a CLI and Node.js interface for a preprocessor that combines various PostCSS plugins.
Compiles CSS packages with:
- postcss-easy-import
- postcss-custom-properties
- postcss-calc
- postcss-color-function
- postcss-apply
- postcss-custom-media
- autoprefixer
Each imported file is linted with postcss-bem-linter and minification is provided by cssnano. Code style can also be checked with stylelint
Additional plugins can be added via the configuration options.
npm install suitcss-preprocessor
suitcss input.css output.css
Usage: suitcss [<input>] [<output>]
Options:
-h, --help output usage information
-V, --version output the version number
-m, --minify minify output with cssnano
-l, --lint ensure code adheres to the SUIT code style
-i, --import-root [path] the root directory for imported css files
-c, --config [path] a custom PostCSS config file
-v, --verbose log verbose output for debugging
-w, --watch watch the input file and any imports for changes
Examples:
# pass an input and output file:
$ suitcss input.css output.css
# configure the import root directory:
$ suitcss --import-root src/css input.css output.css
# watch the input file and imports for changes:
$ suitcss --watch input.css output.css
# configure postcss plugins with a config file:
$ suitcss --config config.js input.css output.css
# unix-style piping to stdin and stdout:
$ cat input.css | suitcss | grep background-color
Returns a PostCSS promise
var preprocessor = require('suitcss-preprocessor');
var fs = require('fs');
var css = fs.readFileSync('src/components/index.css', 'utf8');
preprocessor(css, {
root: 'path/to/css',
minify: true,
}).then(function(result) {
fs.writeFileSync('build/bundle.css', result.css);
});- Type:
String - Default:
process.cwd()
Where to resolve imports from. Passed to postcss-import.
- Type:
Function - Default: identity (it does nothing)
Before preprocessing debug is invoked on the postcss plugins array.
This allows you to pass a postcss-debug instance.
var preprocessor = require('suitcss-preprocessor');
var createDebugger = require('postcss-debug').createDebugger;
var debug = createDebugger();
preprocessor(css, {
debug: debug
}).then(function () {
debug.inspect();
});N.B. debug should always take one argument that is plugins and eventually return it:
function debug(plugins) {
// do something with plugins here
return plugins;
}- Type:
Boolean - Default:
false
Ensure code conforms to the SUIT code style by using the stylelint-config-suitcss package.
Stylelint configuration
options can also be
overridden but this requires the stylelint-config-suitcss to be installed
locally in your package.
{
lint: true,
stylelint: {
extends: 'stylelint-config-suitcss',
rules: {
indentation: [4, 'tab'],
}
}
}- Type:
Boolean - Default:
false
If set to true then the output is minified by cssnano.
- Type:
Object - Default:
undefined
Options that are passed directly to postcss, as per the documentation.
{
postcss: {from: 'filename.css'}
}- Type:
Array - Default:
undefined
A list of plugins that are passed to PostCSS. This can be used to add new plugins and/or reorder the defaults
{
use: ['postcss-at2x', 'postcss-property-lookup']
}- Type:
Object - Default:
undefined
Property matching the name of a PostCSS plugin that has options for that plugin
{
autoprefixer: {
browsers: ['> 1%', 'IE 7'],
cascade: false
},
'postcss-calc': { preserve: true }
}Creating a configuration file allows options to be passed to the individual PostCSS plugins. It can be passed to the suitcss CLI via the -c flag and can be either JavaScript or JSON
module.exports = {
root: 'path/to/css',
autoprefixer: { browsers: ['> 1%', 'IE 7'], cascade: false },
'postcss-calc': { preserve: true }
}{
"root": "path/to/css",
"autoprefixer": { "browsers": ["> 1%", "IE 7"], "cascade": false },
"postcss-calc": { "preserve": true }
}Options are merged recursively with the defaults. For example, adding new plugins to the use array will result in them being merged alongside the existing ones.
By default the preprocessor uses all necessary plugins to build SUIT components. However additional plugins can be installed into a project and then added to the use array.
Note: This will not work with the preprocessor installed globally. Instead rely on the convenience of npm run script
module.exports = {
use: [
'postcss-property-lookup'
]
};{
"name": "my-pkg",
"version": "0.1.0",
"dependencies": {
"postcss-property-lookup": "^1.1.3",
"suitcss-preprocessor": "^0.5.0"
},
"scripts": {
"preprocess": "suitcss -c myconfig.js index.css build/built.css"
}
}npm run preprocess
If duplicate plugins are used they will be removed, but the new order will be respected. This is useful if you need to change the default order:
// Default order
var defaults = [
'postcss-easy-import',
'postcss-custom-properties',
'postcss-calc',
'postcss-color-function',
'postcss-custom-media',
'postcss-apply',
'autoprefixer',
'postcss-reporter'
];
// config
module.exports = {
use: [
'postcss-at2x',
'postcss-calc',
'autoprefixer',
'postcss-reporter'
]
};
var result = [
'postcss-easy-import',
'postcss-custom-properties',
'postcss-color-function',
'postcss-custom-media',
'postcss-apply',
'postcss-at2x',
'postcss-calc',
'autoprefixer',
'postcss-reporter'
];By default the preprocessor uses the SUIT browserslist configuration:
> 1%, last 2 versions, safari > 6, ie > 9, ios > 6, android > 4.3, samsung > 3, chromeandroid > 50
The preprocessor doesn't attempt to find any browserslist config file.
Instead you can customise the browsers list via configuration file.
Based on Myth by Segment.io.