LintLens - VSCode extension
Augment your ESLint rules in Visual Studio Code — Adds metadata and usage information beside each ESLint rule.
Adds details beside each ESLint rule in your configuration file (including plugins) located anywhere in your workspace folders (supports multiple config files, and even multiple versions of ESLint and plugins).
Displays detailed information (including usage schema information and a link to the official docs page) in a hover container for each rule.
Adds intellisense (autocomplete) for rule IDs and for simple rule values (complex rule value intellisense MIGHT be added in the future)
Adds rule value validation
Supports all configuration file formats currently supported by ESLint
- Flat Config - use
eslint.config.js at the root and export an array containing your configurations.
- YAML - use
.eslintrc.yml (or any other yaml file in your workspace) to define the configuration structure.
- JSON - use
- Deprecated - use
.eslintrc, which can be either JSON or YAML.
- package.json - create an
eslintConfig property in your
package.json file and define your configuration there.
If you are new to ESLint check the documentation.
Hover for more information on each rule:
Auto-updates as you type:
In an effort to support all possible plugins and to keep size small, this extension uses both ESLint and ESLint plugins installed in the opened workspace folder(s). Due to restrictions in vscode, this extension does not support globally installed packages.
- Does not support globally installed eslint or plugin packages (must be installed in the currently open workspace)
- ESLint v4.15.0 added an official location for rules to store a URL to their documentation in the rule metadata in eslint/eslint#9788. This adds the URL to all the existing rules so anything consuming them can know where their documentation is without having to resort to external packages to guess. If your plugin hasn't included this metadata, its possible you have an older version that needs to be updated.
- Parsing js configs (flat and legacy) is somewhat limited, but should work in almost all cases.
- Simple exporting of a config works
- Exporting from a variable works
- Finding rules through rest spread works
- rule option validation does not work when variables are used
- Beyond that, parsing could be improved
- Additionally, the language mode must match
- Intellisense does not work for YAML config files
- Rule option validation does not work for YAML config files
- Mistakenly activates for stylelint config files when filename does not contain