node_modules/stylelint/docs/user-guide/ignore-code
Ignoring code
You can ignore:
- within files
- files entirely
Within files
You can temporarily turn off rules using special comments in your CSS. For example, you can either turn all the rules off:
/* stylelint-disable */ a {} /* stylelint-enable */
Or you can turn off individual rules:
/* stylelint-disable selector-no-id, declaration-no-important */ #id { color: pink !important; } /* stylelint-enable selector-no-id, declaration-no-important */
You can turn off rules for individual lines with a /* stylelint-disable-line */
comment, after which you do not need to explicitly re-enable them:
#id { /* stylelint-disable-line */ color: pink !important; /* stylelint-disable-line declaration-no-important */ }
You can also turn off rules for the next line only with a /* stylelint-disable-next-line */
comment, after which you do not need to explicitly re-enable them:
#id { /* stylelint-disable-next-line declaration-no-important */ color: pink !important; }
stylelint supports complex, overlapping disabling & enabling patterns:
/* stylelint-disable */ /* stylelint-enable foo */ /* stylelint-disable foo */ /* stylelint-enable */ /* stylelint-disable foo, bar */ /* stylelint-disable baz */ /* stylelint-enable baz, bar */ /* stylelint-enable foo */
Caveat: Comments within selector and value lists are currently ignored.
Files entirely
You can use a .stylelintignore
file to ignore specific files. For example:
**/*.js vendor/**/*.css
The patterns in your .stylelintignore
file must match .gitignore
syntax. (Behind the scenes, node-ignore
parses your patterns.) Your patterns in .stylelintignore
are always analyzed relative to process.cwd()
.
stylelint looks for a .stylelintignore
file in process.cwd()
. You can also specify a path to your ignore patterns file (absolute or relative to process.cwd()
) using the --ignore-path
(in the CLI) and ignorePath
(in JS) options.
Alternatively, you can add an ignoreFiles
property within your configuration object.