TypeScript linter flagging implicit global method calls
Built for TypeScript developers in large codebases who want to catch accidental global method shadowing at compile time.
“I just spent 2 hours tracking down this issue: - We have a class with a prototype method called `focus()` - Our code was calling `focus()`, but it should ha…”
The receipts — real demand
“I just spent 2 hours tracking down this issue: - We have a class with a prototype method called `focus()` - Our code was calling `focus()`, but it should have been calling `this.focus()` - The code compiled fine, because `window.focus()` shares the same signature as our `focus()` method Is there a way to throw a compile time error when implicitly accessing global methods (on `window`, `global`, etc.)? If n…”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
TypeScript developers in large codebases hunting subtle scope bugs. No search volume, but the pain is real and specific—a single 2-hour debugging session suggests the problem exists but may be niche. Feasibility 8/10 indicates this is straightforward to build.
Competition & the opening
ESLint with custom rules, TypeScript strict mode. The gap: no purpose-built linter rule for implicit global method shadowing. Competition is low (2/10), meaning existing tools don't address this narrowly enough.
What's hard to build
Minimal. TypeScript AST parsing is well-documented. The hard part is user adoption—convincing teams to add another linter rule to their workflow when strict mode already catches many issues.
Why now
TypeScript's type system catches structural errors but misses runtime shadowing bugs that only surface in production.
How you'd monetize
$99/year SaaS linter plugin