A visual tool for inspecting and understanding your ESLint flat configs.
1.3k
Stars
57
Forks
18
Open issues
30
Contributors
AI Analysis
ESLint Config Inspector is a visual debugging tool that helps developers understand and interact with ESLint flat configurations through an interactive web interface. It serves developers who need to troubleshoot, validate, or document their ESLint configurations, and is particularly valuable for teams adopting ESLint's newer flat config format. This tool is not for end users but specifically for developers maintaining linting standards in their projects.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
ESLint's official visual debugger for flat configs—lightweight inspection tool with steady adoption among developers migrating to ESLint 9+
ESLint Config Inspector is a visual web-based tool for inspecting, understanding, and debugging ESLint flat configurations. Built by the ESLint core team, it solves the problem of flat-config complexity by providing interactive rule visualization, file matching preview, and configuration snapshots. Adoption appears concentrated among developers actively using ESLint 9+ flat configs; used by projects with ESLint as a direct dependency.
Created March 2024 as ESLint's official response to the complexity of the new flat config format (eslint.config.js). Timing aligns with ESLint 9's release and deprecation of the legacy .eslintrc format, addressing a specific pain point in the migration journey.
Star count (1,318) reflects steady, modest growth over ~2 years rather than explosive adoption. Growth appears tied to ESLint 9 adoption curve, not viral adoption. Last push on 2026-07-02 indicates active maintenance. Low recent star velocity (2 stars in last 7 days) suggests stable, established usage rather than early-growth phase.
Adoption not verified. No documented enterprise users, case studies, or download metrics in README. NPM download badge referenced but values not included in excerpt. Project is official ESLint tooling (distributed via @eslint scoped package), which likely ensures some baseline adoption among ESLint 9 users, but real-world usage scale remains opaque. Sponsorship by companies (Automattic, Shopify, Vite ecosystem) suggests institutional backing rather than market-driven adoption.
Likely a Nuxt 3 + Vue web application frontend paired with a Node CLI backend. Uses devframe for dev server and RPC transport between CLI and web UI. Architecture appears decoupled: web UI loads and displays config snapshots; static build capability suggests SPA architecture. Based on README, implementation uses UnoCSS for styling and ESLint's own linting for tooling consistency.
Not documented in README. No mention of test suites, CI/CD pipelines, or coverage metrics. Test strategy is not transparent.
Last push on 2026-07-02 (current date) indicates active maintenance. Contribution guidelines reference ESLint Contributor Guidelines, suggesting structured governance. Issue tracker is mentioned as available. However, slow star velocity and lack of public roadmap/issue activity in README prevent assessment of development pace or backlog.
ADOPT IF: you are using ESLint 9+ flat configs and need to debug or understand rule application, file matching, or config conflicts; you want an official, maintainer-backed tool for config visualization; your team needs shareable static config documentation. AVOID IF: you are still on ESLint 8 or legacy .eslintrc format (tool requires flat config); you need advanced rule state management or full linting pipeline inspection beyond config structure; you work in offline-only environments without npm/local hosting. MONITOR IF: you are evaluating ESLint 9 migration readiness; you want to confirm adoption maturity before making it a standard team tool; you need evidence of large-scale production usage beyond core ESLint audience.
Independent dimensions
Mainstream potential
3/10
Technical importance
6/10
Adoption evidence
4/10
- Tight coupling to ESLint 9+ flat config format; may become obsolete if ESLint ecosystem shifts again, or adds friction if major config changes occur.
- Adoption not verified at scale; limited evidence of usage beyond ESLint core community. If adoption remains niche, feature requests and bug fixes may slow.
- Test coverage not documented; maintenance quality at code level cannot be assessed from README alone.
- Single-purpose tool with narrow use case; addressable only during config authoring/debugging phase, not runtime value.
- No public roadmap or issue activity visible in README; unclear how user feedback shapes development priorities.
Likely to remain a stable, narrow-purpose tool within the ESLint ecosystem. Growth will follow ESLint 9 adoption curve, not diverge from it. May see gradual feature additions (e.g., config recommendations, rule interaction analysis) but unlikely to expand beyond config debugging domain. Will remain officially maintained as long as flat configs are ESLint's standard.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- TypeScript
- License
- Apache-2.0
- Last updated
- 1d ago
- Created
- 28mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
No open issues — clean slate.
Top contributors
Recent releases
Similar repos
zh-lx/code-inspector
Code Inspector is a developer tool that enables clicking DOM elements in the...
vuejs/eslint-plugin-vue
The official ESLint plugin for Vue.js that enforces linting rules specific to...
standard/eslint-config-standard
This package provides the ESLint configuration for JavaScript Standard Style, a...
microsoft/vscode-eslint
This is the official VS Code extension that integrates ESLint into the editor,...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
eslint/config-inspector
this
|
1.3k | — | TypeScript | 8/10 | 1d ago |
|
zh-lx/code-inspector
|
3k | — | TypeScript | 8/10 | 1d ago |
|
vuejs/eslint-plugin-vue
|
4.6k | — | TypeScript | 8/10 | 7d ago |
|
standard/eslint-config-standard
|
2.7k | — | TypeScript | 8/10 | 1w ago |
|
microsoft/vscode-eslint
|
1.9k | — | TypeScript | 8/10 | 1w ago |
|
eslint/eslint
|
27.4k | — | JavaScript | 9/10 | 14h ago |
Broader use case: built-in linting in editor. Config Inspector is complementary (debugging tool) rather than competitive; operates outside IDE. Different user phase: extension for development workflow, Inspector for config understanding.
Inspector is an auxiliary tool for ESLint, not a replacement. ESLint CLI remains the core linting engine; Inspector adds visibility layer only.
Pre-built opinionated config vs. debugging tool for any config. These serve different purposes: antfu provides a configuration template; Inspector helps users understand their own (any) configuration.
Integration layer between two formatters, not config inspection. Does not overlap in use case.
Broader visual code inspection tool. ESLint Config Inspector is narrower (ESLint configs only) and official; code-inspector is general-purpose element inspector.
