Plugins are rules and sets of rules built by the community.
We recommend your plugin adheres to stylelint's conventions for:
Your plugin's rule name must be namespaced, e.g.
your-namespace/your-rule-name, to ensure it never clashes with the built-in rules. If your plugin provides only a single rule or you can't think of a good namespace, you can use
plugin/my-rule. You should document your plugin's rule name (and namespace) because users need to use them in their config.
stylelint.createPlugin(ruleName, ruleFunction) to ensure that your plugin is set up properly alongside other rules.
For your plugin rule to work with the standard configuration format,
ruleFunction should accept 2 arguments:
- the primary option
- optionally, a secondary options object
If your plugin rule supports autofixing, then
ruleFunction should also accept a third argument:
context. You should try to support the
disableFix option in your secondary options object. Within the rule, don't perform autofixing if the user has passed a
disableFix option for your rule.
ruleFunction should return a function that is essentially a little PostCSS plugin. It takes 2 arguments:
- the PostCSS Root (the parsed AST)
- the PostCSS LazyResult
You'll have to learn about the PostCSS API.
You can return a
Promise instance from your plugin function to create an asynchronous rule.
You should use
jest-preset-stylelint to test your plugin. The preset exposes a global
testRule function that you can use to efficiently test your plugin using a schema.
However, if your plugin involves more than just checking syntax you can use stylelint directly.
Alternatively, if you don't want to use Jest you'll find more tools in awesome stylelint.
stylelint exposes some useful utilities.
Adds violations from your plugin to the list of violations that stylelint will report to the user.
stylelint.utils.report to ensure your plugin respects disabled ranges and other possible future features of stylelint. Do not use PostCSS's
node.warn() method directly.
Tailors your messages to the format of standard stylelint rules.
Validates the options for your rule.
Checks CSS against a standard stylelint rule within your own rule. This function provides power and flexibility for plugins authors who wish to modify, constrain, or extend the functionality of existing stylelint rules.
It accepts an options object and a callback that is invoked with warnings from the specified rule. The options are:
ruleName: the name of the rule you are invoking
ruleSettings: settings for the rule you are invoking
root: the root node to run this rule against
Use the warning to create a new warning from your plugin rule that you report with
For example, imagine you want to create a plugin that runs
at-rule-no-unknown with a built-in list of exceptions for at-rules provided by your preprocessor-of-choice:
All of the rule functions are available at
stylelint.rules. This allows you to build on top of existing rules for your particular needs.
A typical use-case is to build in more complex conditionals that the rule's options allow for. For example, maybe your codebase uses special comment directives to customize rule options for specific stylesheets. You could build a plugin that checks those directives and then runs the appropriate rules with the right options (or doesn't run them at all).
All rules share a common signature. They are a function that accepts two arguments: a primary option and a secondary options object. And that functions returns a function that has the signature of a PostCSS plugin, expecting a PostCSS root and result as its arguments.
Here's an example of a plugin that runs
color-hex-case only if there is a special directive
@@check-color-hex-case somewhere in the stylesheet:
If your plugin can accept an array as its primary option, you must designate this by setting the property
primaryOptionArray = true on your rule function. For more information, check out the "Working on rules" doc.
In addition to the standard parsers mentioned in the "Working on rules" doc, there are other external modules used within stylelint that we recommend using. These include:
- normalize-selector: normalize CSS selectors.
- postcss-resolve-nested-selector: given a (nested) selector in a PostCSS AST, return an array of resolved selectors.
Have a look through stylelint's internal utils and if you come across one that you need in your plugin, then please consider helping us extract it out into an external module.
You should express, within the
peerDependencies key (and not within the
dependencies key) of your plugin's
package.json, what version(s) of stylelint your plugin can be used with. This is to ensure that different versions of stylelint are not unexpectedly installed.
For example, to express that your plugin can be used with stylelint versions 7 and 8:
To make a single module provide multiple rules, export an array of plugin objects (rather than a single object).
stylelint-plugin keyword within your