Developer tools1 sources·Published

A whole-project type error dashboard for large TypeScript/JavaScript codebases

Developers on large TS/JS repos change a shared function signature, break hundreds of files, but VS Code's Problems panel only shows errors for opened files, forcing them into a terminal/editor back-and-forth. A standalone tool that precomputes and lists all project-wide type errors with clickable navigation fills this gap.

Score 721 sourcesConfidence 78%

The problem

In projects with hundreds of files, a single signature change breaks many closed files. The editor only surfaces diagnostics for open files, so developers must run make/tsc in a terminal, then manually hunt for the right line in the right file, repeatedly bouncing between terminal and editor.

What could be built

A background indexer / language-server wrapper or CLI that runs full-project TypeScript compilation, caches all diagnostics across open and closed files, and exposes them in a single sortable, clickable list (or overlay) that jumps to the offending file and line.

Who it's for

TypeScript developers on large multi-package monoreposFrontend/backend engineers maintaining repos with hundreds of nested files

Who is talking1

Related topics

TypeScriptVS CodeProblems panelmonorepo diagnosticsproject-wide linting

Summaries are AI-generated. The original words are in the threads above.