VS Code extension that builds a persistent, queryable error graph across the whole TypeScript project and shows cascading impact of a change before you save
TypeScript's type system already encodes the dependency graph; nobody has turned that into a pre-save impact map that developers actually want to stare at
Built for TypeScript/JavaScript developers at mid-to-large companies working on monorepos or projects with hundreds of files who need to understand the full impact of refactoring changes..
Shift from reactive error list to predictive change-impact visualization so engineers see blast radius of a refactor before it propagates
“I am using VS Code on a project at work that has hundreds of files and many layers of nested sub-directories. I frequently make changes that break many files, s…”
The receipts — real demand
“I am using VS Code on a project at work that has hundreds of files and many layers of nested sub-directories. I frequently make changes that break many files, such as changing the call signature of a commonly used method. Since the project is entirely typescript, it is useful to be able to open the "Problems" view and see the errors and warnings my change caused in the files I have open. However, because of the size …”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
demand score 6.3 — the receipts are below
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
Mid-to-large company TypeScript/JavaScript developers working on monorepos with hundreds of files need visibility into how their refactoring changes ripple across the codebase. No search volume signal; demand exists but appears to be concentrated in large engineering teams, not a mass-market segment.
Competition & the opening
VS Code's built-in 'Find All References' and TypeScript language server provide basic impact analysis; competitors like Codemod and AST-based tools exist for structural changes. The gap is real-time, visual, unified error-impact tracking that doesn't require leaving the editor or running external tooling.
What's hard to build
Building accurate cross-file dependency resolution and error propagation at the AST or type-system level requires deep TypeScript compiler knowledge and significant performance tuning to avoid blocking the editor. Monorepo setups vary widely (Turborepo, Nx, Yarn Workspaces), making generalizable integration hard without close collaboration with users on their specific toolchain.
Why now
Large TypeScript projects expose VS Code's limitation in full-project error aggregation; better indexing now makes this solvable.
How you'd monetize
one-time $29 extension or $4.99/mo subscription