Skip to content
You are viewing the v1 archive. For current setup guidance, use the v3 docs; the v2 release is preserved at /v2/.

Inspector

The repository includes the ESLint config inspector so you can see the final merged config instead of guessing which layer is responsible for a rule.

Terminal window
npm run inspector
  • Confirming whether a rule comes from the core package, a framework package, or an optional integration.
  • Verifying the order of config layers.
  • Debugging conflicts between TypeScript, framework packages, and formatting tools.
  • Understanding what strict: true or a preset changed in the final output.
  • Start with the inspector when the final rule value is surprising.
  • Compare the result with the docs page for the relevant framework or optional integration.
  • Use playgrounds to reproduce the issue in a real project shape.

Did this page help?

One click helps us spot documentation that needs another pass. No personal data is sent.