TypeScript 7: When Your Compiler Stops Napping
TypeScript 7 rewrites its compiler in Go: 10x faster, no new syntax, and strict mode by default. Here's the full rundown.
•4 min read
TypeScript 7 rewrites its compiler in Go: 10x faster, no new syntax, and strict mode by default. Here's the full rundown.
There are major releases that change how you write code. And then there's TypeScript 7, which mostly changes how you wait. Spoiler: you'll be waiting a lot less. For years we joked about tsc --watch giving us enough time to contemplate our careers while it ran. Turns out, we finally have some genuinely good news.
Since its inception, TypeScript has had a bit of a "cobbler's children" problem: a compiler written in TypeScript (well, compiled JavaScript), running on Node.js. Efficient enough, but not exactly built for speed on large codebases.
With TypeScript 7, released as stable (GA) on July 8, 2026, Microsoft rewrote the entire compiler and language service in Go. The project was codenamed "Corsa" internally, replacing the old codebase nicknamed "Strada". And no, this isn't a rewrite that changes how the language works: it's a port. The type semantics remain identical to TypeScript 6. You lose (almost) nothing, you just gain an enormous amount of speed.
Why Go instead of Rust, which had been the darling of JS tooling (Turbopack, SWC, etc.)? The team explained they chose Go for two very practical reasons: a code structure close to the original, which allowed a near line-by-line port, and goroutines, which enable parallelizing type checking across multiple cores, a luxury the old single-threaded compiler couldn't afford.
Microsoft reports typical gains between 8x and 12x on full builds. This isn't just a marketing figure from a press release: on the VS Code source code (no small feat), type checking time dropped from 125.7 seconds on TypeScript 6 to 10.6 seconds on TypeScript 7, roughly an 11.9x improvement.
And it's not just full builds that speed up. Opening a file containing errors in the editor is reportedly about 13x faster (17.5s → 1.3s), and loading projects in Visual Studio is about 8x faster.
In short, if your biggest workplace enemy was the VS Code loading screen while the language service woke up, you just won a small personal victory.
Default values become stricter. TypeScript 6.0 had already laid the groundwork by deprecating certain options. With version 7, those deprecations go from warning to hard error. Strict mode becomes the norm, not the exception you enable "someday, I promise."
Installation changes (almost) nothing. You stay on the same typescript package, with the same tsc command. No new binary to learn to love. A simple version bump and you're done, at least in theory.
There's no new syntax. If you were hoping for new keywords or novel typing features, that's not what this release is about. TypeScript 7 is a story of speed, parallelism, and cleanup, not syntactic novelty.
TypeScript 7.0 shipped without a stable programmatic API. In practice, if your stack depends on Vue, Angular (for template typing), Svelte, Astro, or MDX, or tooling that relies on the compiler API like typescript-eslint or ts-morph, you'll need to wait until version 7.1, where Microsoft plans to ship a new API. Suffice to say, not everyone can hop on the train today, and it's actually healthy to take it step by step.
The good news is that the risk is low for type checking itself. Teams that mainly use tsc --noEmit in CI, or that leave transpilation to fast tools like esbuild or SWC (which don't check types, let's be clear, they just strip them), can test right now without much danger. For declaration file generation (--declaration, --build), however, it's better to wait for a more mature version of the emission pipeline.
TypeScript 7 doesn't reinvent the language, it reinvents the wait. It's a careful port, not a type system revolution, but that's precisely what makes it reassuring: your code behaves exactly the same, it just goes ten times faster telling you so. After fourteen years running on its own runtime, TypeScript has traded its bicycle for a race car, and it's still Anders Hejlsberg, the same architect since day one, behind the wheel.
If you're the kind of person who checks email while a tsc --watch runs in the background, get ready to find a new excuse for your coffee break.