This version of
stylelint-webpack-pluginonly works with webpack 5. For webpack 4, see the2.x branch.
This plugin usesstylelint, which helps you avoid errors and enforce conventions in your styles.
To begin, you'll need to installstylelint-webpack-plugin:
npm install stylelint-webpack-plugin --save-devor
yarn add -D stylelint-webpack-pluginor
pnpm add -D stylelint-webpack-plugin[!NOTE]
You also need to install
stylelint >= 13from npm, if you haven't already:
npm install stylelint --save-devor
yarn add -D stylelintor
pnpm add -D stylelint[!NOTE]
If you are using Stylelint 13 rather than 14+, you might also need to install
@types/stylelintas a dev dependency if you encounter Stylelint-related type errors.
Then add the plugin to your webpack configuration. For example:
const StylelintPlugin=require("stylelint-webpack-plugin");module.exports={// ... plugins:[newStylelintPlugin(options)],// ...};Seestylelint's options for the complete list of available options . These options are passed directly tostylelint.
cachetypecache=boolean;trueThe cache is enabled by default to decrease execution time.
cacheLocationtypecacheLocation=string;node_modules/.cache/stylelint-webpack-plugin/.stylelintcacheSpecify the path to the cache location. This can be a file or a directory.
configFiletypecontext=string;undefinedSpecify the config file location to be used bystylelint.
Note:
By default this ishandled by
stylelint.
contexttypecontext=string;compiler.contextA string indicating the root of your files.
excludetypeexclude=string|string[];['node_modules', compiler.options.output.path]Specify the files and/or directories to exclude. Must be relative tooptions.context.
extensionstypeextensions=string|string[];['css', 'scss', 'sass']Specify the extensions that should be checked.
filestypefiles=string|string[];nullSpecify directories, files, or globs. Must be relative tooptions.context. Directories are traversed recursively, looking for files matchingoptions.extensions. File and glob patterns ignoreoptions.extensions.
fixtypefix=boolean;falseIftrue,stylelint will fix as many errors as possible. The fixes are made to the actual source files. All unfixed errors will be reported. SeeAutofixing errors docs.
formattertypeformatter=|string|((results:import("stylelint").LintResult[])=>string);'string'Specify the formatter you would like to use to format your results. See theformatter option.
lintDirtyModulesOnlytypelintDirtyModulesOnly=boolean;falseLint only changed files; skip linting on start.
stylelintPathtypestylelintPath=string;stylelintPath tostylelint instance that will be used for linting.
threadstypethreads=boolean|number;falseSet totrue for an auto-selected pool size based on number of CPUs. Set to a number greater than 1 to set an explicit pool size.
Set tofalse, 1, or less to disable and run only in main process.
By default, the plugin will automatically adjust error reporting depending on the number of Stylelint errors/warnings.
You can still force this behavior by using theemitErrororemitWarning options:
emitErrortypeemitError=boolean;trueThe errors found will always be emitted. To disable, set tofalse.
emitWarningtypeemitWarning=boolean;trueThe warnings found will always be emitted. To disable, set tofalse.
failOnErrortypefailOnError=boolean;trueWill cause the module build to fail if there are any errors. To disable, set tofalse.
failOnWarningtypefailOnWarning=boolean;falseWill cause the module build to fail if there are any warnings, when set totrue.
quiettypequiet=boolean;falseWill process and report errors only, and ignore warnings, when set totrue.
outputReporttypeoutputReport=|boolean|{ filePath?:string|undefined; formatter?:|(string|((results:import("stylelint").LintResult[])=>string))|undefined;};falseWrites the output of the errors to a file - for example, ajson file for use for reporting.
ThefilePath is relative to the webpack config:output.path.
You can pass in a different formatter for the output file. If none is passed in the default/configured formatter will be used.
const outputReport={ filePath:"path/to/file", formatter:"json",};We welcome all contributions!If you're new here, please take a moment to review our contributing guidelines before submitting issues or pull requests.