Course contentsShow
← JavaScript
Lesson 2592 of 2,72352. Linting and FormattingFree lesson

Troubleshooting Editor Integration Issues

Diagnose and fix common problems like extensions not working, outdated configs, or conflicting settings.

Troubleshooting Editor Integration Issues

What you'll learn: How to diagnose and fix the most common problems when ESLint and Prettier extensions refuse to cooperate in your editor.

Even with perfect configuration files, editor integrations can break. Understanding where to look when things go wrong separates productive developers from frustrated ones.

Common Problems and Solutions

Extension Not Running at All

Check the Output panel in your editor (often View → Output, then select ESLint or Prettier from the dropdown). This log reveals whether the extension is even attempting to run. Common causes:

  • Extension disabled – Verify it's enabled in your extensions panel
  • Wrong workspace – Extensions may only activate when a package.json or config file exists in the workspace root
  • Outdated extension – Update to the latest version; older ones may not support newer config formats

Conflicting Settings

When both ESLint and Prettier are enabled with format-on-save, they can fight each other. The solution lives in your workspace settings:

{
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,
  "eslint.format.enable": false
}

Set one formatter as default to avoid conflicts.

Outdated Configuration Not Detected

After changing .eslintrc.js or eslint.config.js, the extension might cache the old version. Restart the ESLint server through your editor's command palette ("ESLint: Restart ESLint Server").

Wrong Node Version or Missing Dependencies

Extensions run ESLint/Prettier using your project's installed version. If node_modules is missing or you're using an incompatible Node version, nothing works. Run npm install and verify your Node version matches package.json's engines field.

Global vs Local Install Confusion

Modern extensions prefer local installs. If you installed ESLint globally but not locally, the extension may fail. Always install locally in your project.

Key Takeaway: Most editor integration issues stem from extension state (restart it), conflicting formatters (pick one default), or missing local dependencies (run npm install). Check the extension's output logs first—they tell you exactly what's broken.