WebStorm ESLint Not Working

How to fix it

Try these in order — the most common fix is first.

1. 1. Install ESLint and a config

   Copy steps
   1. Run npm install --save-dev eslint or npm init @eslint/config@latest in the project
   2. Use eslint.config.js (or .mjs, .cjs, .ts) for ESLint 9 and later, .eslintrc.* for 8 and earlier
   Did this fix it? Yes No

2. 2. Enable ESLint in settings

   Copy steps
   1. Press Ctrl+Alt+S and open Languages & Frameworks | JavaScript | Code Quality Tools | ESLint
   2. Choose Automatic ESLint configuration, or Manual to set package, working directories and config file yourself
   3. Optionally enable Run eslint --fix on save
   Did this fix it? Yes No

3. 3. Fix how problems are highlighted

   Copy steps
   1. Open Editor | Inspections | JavaScript | Code quality tools | ESLint
   2. Clear Use rule severity from the configuration file if you want WebStorm severities
   Did this fix it? Yes No

Symptoms

No ESLint warnings appear in the editor or Problems tool window, or fixes do not apply on save.

Why it happens

• ESLint not installed in the project
• Config file name does not match the ESLint version (eslint.config.js for 9+, .eslintrc.* for 8 and earlier)
• Automatic configuration picks the wrong package or folder
• No Node.js interpreter configured
• Severity overridden by the config file

This guide also covers

• webstorm eslint not working
• eslint not working in webstorm
• webstorm eslint config not found

Other WebStorm errors

• WebStorm Node.js Interpreter Not Configured
• WebStorm Prettier Not Working
• WebStorm TypeScript Language Service Errors and Slowness
• WebStorm Indexing Takes Forever
• WebStorm High Memory Usage: Increase Heap Size
• WebStorm Debugger Not Attaching or Breakpoints Not Hit
• WebStorm License Activation and Login Problems