You can use stylelint on the command line. For example:
npx stylelint "**/*.css"
Use npx stylelint --help
to print the CLI documentation.
In addition to the standard options, the CLI accepts:
The process exits without throwing an error when glob pattern matches no files.
Force enabling/disabling of color.
Pattern of files to ignore (in addition to those in .stylelintignore
).
Path of file to write a report. stylelint outputs the report to the specified filename
in addition to the standard output.
Print the configuration for the given path. stylelint outputs the configuration used for the file passed.
Only register violations for rules with an "error"-level severity (ignore "warning"-level).
Accept stdin input even if it is empty.
Show the currently installed version of stylelint.
The CLI expects input as either a file glob or process.stdin
. It outputs formatted results into process.stdout
.
Be sure to include quotation marks around file globs.
Recursively linting all .css
files in the foo
directory:
stylelint "foo/**/*.css"
Linting all .css
, .scss
, and .sass
files:
stylelint "**/*.{css,scss,sass}"
Linting stdin
:
echo "a { color: pink; }" | stylelint
Linting all .css
files except those within docker
subfolders, using negation in the input glob:
stylelint "**/*.css" "!**/docker/**"
Caching processed .scss
files foo
directory:
stylelint "foo/**/*.scss" --cache --cache-location "/Users/user/.stylelintcache/"
Linting all .css
files in the foo
directory, then writing the output to myTestReport.txt
:
stylelint "foo/*.css" --output-file myTestReport.txt
Using bar/mySpecialConfig.json
as config to lint all .css
files in the foo
directory and any of its subdirectories:
stylelint "foo/**/*.css" --config bar/mySpecialConfig.json
Recursively linting all .css
files in the foo
directory using a custom syntax:
stylelint "foo/**/*.css" --customSyntax path/to/my-custom-syntax.js
Ensure output on successful runs:
stylelint -f verbose "foo/**/*.css"
The CLI can exit the process with the following exit codes:
1
- something unknown went wrong2
- there was at least one rule violation or CLI flag error78
- there was some problem with the configuration file