Download this extension from the VS Gallery
or get the CI build.
See the change log for changes and road map.
Table of Contents
- Lint files using ESLint on file open/save
- Visually mark errors/warnings in open document
- Include tooltip content with info on errors/warnings
- Fully integrated with Visual Studio error list
- ESLint installed locally (per project) or globally (ESLint added to
- A valid configuration located in the current project directory (local) or your user home directory (
The default behavior is set to use a local ESLint installation and config.
If you instead wish to use a global installation and/or config, you can enable each respective option in Visual Studio under
Please note that enabling the option
Use global ESLint installation instead of local has no effect on the use of a config file (and vice versa).
A local config will still be used unless
Use personal ESLint config instead of local is also enabled in options.
The closest installation/config found relative to the file being linted will always be used.
node_modules directory or
.eslintrc file is found in the same directory as the file being linted,
VisualLinter will try and resolve the paths from ancestor directories up to, and including the root directory (e.g.
C:\\ on Windows).
For instance, suppose you have the following structure:
│ └── source.js
source.js is being opened or saved the
.eslintrc file at the root of the project will be used as its config.
test.js is being opened or saved the
.eslintrc file in the
tests/ directory will be used as its config.
If there are multiple config files in the same directory,
VisualLinter will only use one. The priority order is: