An ESLint plugin for linting ESLint plugins
You'll first need to install ESLint:
$ npm i eslint --save-dev
Next, install eslint-plugin-eslint-plugin
:
$ npm install eslint-plugin-eslint-plugin --save-dev
Note: If you installed ESLint globally (using the -g
flag) then you must also install eslint-plugin-eslint-plugin
globally.
Add eslint-plugin
to the plugins section of your .eslintrc
configuration file. You can omit the eslint-plugin-
prefix:
{
"plugins": [
"eslint-plugin"
]
}
Then configure the rules you want to use under the rules section.
{
"rules": {
"eslint-plugin/no-deprecated-report-api": "error"
}
}
โ๏ธ indicates that a rule is recommended for all users. ๐ indicates that a rule is fixable.
Name | โ๏ธ | ๐ | Description |
---|---|---|---|
consistent-output | Enforce consistent use of output assertions in rule tests | ||
fixer-return | โ๏ธ | Expected fixer function to always return a value. | |
no-deprecated-context-methods | ๐ | Disallows usage of deprecated methods on rule context objects | |
no-deprecated-report-api | โ๏ธ | ๐ | disallow use of the deprecated context.report() API |
no-identical-tests | โ๏ธ | ๐ | disallow identical tests |
no-missing-placeholders | โ๏ธ | Disallow missing placeholders in rule report messages | |
no-unused-placeholders | โ๏ธ | Disallow unused placeholders in rule report messages | |
no-useless-token-range | โ๏ธ | ๐ | Disallow unnecessary calls to sourceCode.getFirstToken and sourceCode.getLastToken |
prefer-output-null | ๐ | disallows invalid RuleTester test cases with the output the same as the code. | |
prefer-placeholders | disallow template literals as report messages | ||
prefer-replace-text | prefer using replaceText instead of replaceTextRange. | ||
report-message-format | enforce a consistent format for rule report messages | ||
require-meta-docs-url | ๐ | require rules to implement a meta.docs.url property | |
require-meta-fixable | โ๏ธ | require rules to implement a meta.fixable property | |
require-meta-type | require rules to implement a meta.type property | ||
test-case-property-ordering | ๐ | Requires the properties of a test case to be placed in a consistent order | |
test-case-shorthand-strings | ๐ | Enforce consistent usage of shorthand strings for test cases with no options |
Presets are enabled by adding a line to the extends
list in your config file. For example, to enable the recommended
preset, use:
{
"extends": [
"plugin:eslint-plugin/recommended"
]
}
-
recommended
enables all recommended rules from this plugin. -
rules-recommended
enables all recommended rules that are aimed at linting ESLint rule files. -
tests-recommended
enables all recommended rules that are aimed at linting ESLint test files. -
all
enables all rules in this plugin. -
rules
enables all rules that are aimed at linting ESLint rule files. -
tests
enables all rules that are aimed at linting ESLint test files.
The list of recommended rules will only change in a major release of this plugin. However, new non-recommended rules might be added in a minor release of this plugin. Therefore, the using the all
, rules
, and tests
presets is not recommended for production use, because the addition of new rules in a minor release could break your build.