Developers miss lint errors outside the files open in their editor
Developers using editor linting extensions want to see errors across a whole project, but some extensions report diagnostics only for files they have opened. They then have to run a linter in the terminal and hunt through its output to find the right file and line. The signals point most strongly to an on-demand, workspace-wide linting workflow; related requests also mention configuration and runtime friction.
For developers who rely on editor-based linting. Mentioned from Jun 2016 to Sep 2026 on Bluesky, GitHub and Hacker News.
11 different people described this problem in 8 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.6/10
- Frequency
- 9.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.6/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I then need to perform the fun dance between my terminal and VS Code, searching for the right line in the right file before I can fix the problem
I noticed ESLint only shows errors of files you've opened. Is there a way to force it to scan all files in the project?
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 9 more quotes from people who have this problem
- Current workarounds, existing solutions and risks