TypeScript 7.0 Ships a Go-Based Compiler — and a 74-Case Fidelity Margin
Microsoft is releasing TypeScript 7.0, a ground-up rewrite of the compiler in Go, with 6.0 as a bridge release. It matches the legacy typechecker on all but 74 of roughly 20,000 test cases.
TL;DR — Microsoft is releasing TypeScript 7.0 ("Project Corsa"), a native rewrite of the compiler in Go targeting major gains in speed, memory, and parallelism, with TypeScript 6.0 acting as a 2026 bridge release.
TypeScript is now the language a large share of the web is effectively authored in. It also carries a known performance ceiling: on large codebases, compiler and editor tooling degrade badly. Microsoft's response is unusually aggressive for a dependency this central — a full rewrite of the compiler in a different language. That language is Go, the program is codenamed Corsa, and it ships as TypeScript 7.0. The wager is that one of the most depended-on dev tools in existence can be re-implemented without breaking the projects built on it.
Two-version migration path
Microsoft is sequencing the move across two releases, and the distinction is operationally important for anyone maintaining TypeScript code:
- TypeScript 6.0 — the final release on the existing JavaScript/TypeScript codebase; a compatibility bridge.
- TypeScript 7.0 — the native Go build, targeting major wins in performance, memory usage, and parallelism.
Per InfoWorld, Microsoft principal product manager Daniel Rosenwasser described the sequencing directly: "You can think of TypeScript 6.0 as a 'bridge' release between the TypeScript 5.9 line and 7.0... 6.0 will deprecate features to align with 7.0." The division of labor: 6.0 flags what is changing, 7.0 delivers the new engine.
The fidelity number
For a typechecker, correctness is the product — a fast but subtly wrong compiler is worse than a slow correct one. So the decisive metric is not a speedup but a fidelity figure. Per InfoWorld, across roughly 20,000 compiler test cases (about 6,000 producing errors), TypeScript 7.0 matches the behavior of TypeScript 5.9 in all but 74 cases. For a clean-room reimplementation, that is a high bar cleared — the evidence that makes migration credible rather than aspirational.
| Item | Detail |
|---|---|
| Codename | Project Corsa |
| New language | Go |
| Bridge release | TypeScript 6.0 |
| Native release | TypeScript 7.0 |
| Test fidelity | Matches 5.9 on all but 74 of ~20,000 cases |
Why Go
Microsoft's own materials are more restrained than the surrounding hype; the InfoWorld write-up frames the goals as "performance, memory usage, and parallelism" rather than a single marketing multiplier. Go supplies straightforward concurrency and predictable memory behavior — both directly applicable to typechecking a million-line monorepo where the legacy single-threaded design saturates. The strategic note is equally notable: Microsoft chose Google's language to rebuild Microsoft's language, a pragmatic engineering call that reflects how mature the open-source toolchain has become. The work runs in the open on GitHub, where the new compiler is continuously tested against the old one's suite.
Developer impact
The day-to-day payoff is concrete: faster editor cold starts, quicker type checking in CI, and headroom for codebases that currently strain the tooling. Migration friction concentrates in 6.0's deprecations — act on those warnings and 7.0 should be a drop-in upgrade for most projects; ignore them and you will encounter a subset of those 74 edge cases firsthand.
FAQ
What is Project Corsa?
Project Corsa is Microsoft's codename for the native rewrite of the TypeScript compiler in Go, shipped as TypeScript 7.0. It aims to substantially improve compile speed, memory use, and parallelism over the current JavaScript-based implementation.
Do I need to change my code for TypeScript 7.0?
Most projects will not need major changes, but TypeScript 6.0 is a bridge release that deprecates features to align with 7.0. Following those deprecation warnings in 6.0 is the path to a smooth move to the native compiler.
Is the new TypeScript compiler reliable?
Early evidence is strong: across roughly 20,000 compiler test cases, the Go-based TypeScript 7.0 matches the existing 5.9 typechecker in all but 74 cases, indicating very high behavioral fidelity.
Sources: InfoWorld, Microsoft/TypeScript on GitHub.
Image: Microsoft, Apache License 2.0, via Wikimedia Commons.
← Back to all posts