ESLint Editor Extensions
What you'll learn: How to install and configure ESLint extensions in popular code editors so you see linting errors as you type, not just when you run commands.
Why Editor Extensions Matter
You've learned to run ESLint from the command line and integrate it with Prettier, but waiting to see errors until you manually lint is slow and disruptive. Editor extensions bring ESLint's feedback directly into your coding environment, highlighting issues with squiggly underlines and showing error messages on hover—just like spell-check in a word processor.
Setting Up in Popular Editors
VS Code
- Open the Extensions panel (Ctrl+Shift+X / Cmd+Shift+X)
- Search for "ESLint" by Microsoft
- Click Install
- The extension automatically detects your
.eslintrcoreslint.config.jsfile and starts linting open files
WebStorm/IntelliJ
ESLint support is built-in:
- Go to Preferences → Languages & Frameworks → JavaScript → Code Quality Tools → ESLint
- Enable "Automatic ESLint configuration"
- WebStorm will find your local ESLint installation and config automatically
Other Editors
Most modern editors (Sublime Text, Atom, Vim with plugins) offer ESLint extensions through their package managers—search for "ESLint" and follow installation instructions.
What You Get
Once installed, errors appear inline as you type: unused variables get grayed out, style violations show yellow warnings, and serious issues display red squiggles. Hovering reveals the rule name and description. Many extensions also support quick fixes, letting you apply --fix suggestions with a keyboard shortcut.
Key Takeaway: ESLint editor extensions transform linting from a separate build step into real-time feedback, catching errors the moment you write them and dramatically speeding up your workflow.