TypeScript 7's Compiler Rewrite Cuts Type-Checking Time 8-10x

TypeScript 7's Go-rewritten compiler cut type-checking on a 159,320-line Next.js app from 7.32 seconds to 0.78 seconds, per testing by paddo.dev.

At that speed, checking stops being a pre-commit gate and becomes something that runs after every edit. For a coding agent, the error surfaces while the reasoning behind it is still live, not as a stack trace three tool calls later.

A smaller 9,140-line Astro blog saw the same pattern, dropping from 2.56 seconds to 0.32 seconds, an 8x gain, per the same testing.

CPU utilization during the check rose from roughly 156% to 422% while total CPU time fell, evidence of a real parallel rewrite.

Wiring tsc into a PostToolUse hook so it fires on every .ts edit takes about ten minutes.

Yes, but the riskier upgrade is TypeScript 6, whose silent types-config change produced 37 spurious errors on one codebase and broke type resolution on another.

Setting types explicitly in tsconfig avoids it. An agent handed 37 phantom errors won't know the difference; it'll confidently patch code that was never broken.

The same argument shows up elsewhere in July 2026 coverage. Siemens and NVIDIA's EDA agents check output against deterministic engines instead of their own reasoning. Marktechpost's write-up on KAT-Coder-V2.5 argues agentic coding is bottlenecked by verifiable environments, not model scale.