TypeScript 7 on Go: Up to 12x Faster Builds
For years, TypeScript was a language written in TypeScript. With version 7, Microsoft moved the compiler and language tooling to Go.This isn't a cosmetic refactor. It's the kind of architectural change you feel within seconds.
What changed under the hood
TypeScript 7 runs as a native application, uses shared-memory multithreading, and can parallelize work such as parsing, type-checking, and emitting files.The team didn't reinvent the compiler. They ported the previous implementation as faithfully as they could, so TypeScript 7 behaves like TypeScript 6. Speed isn't much of a win if it ships with surprises.
How much faster is it?
On large codebases, full builds are typically 8 to 12 times faster.In Microsoft's benchmarks, the VS Code codebase went from 125.7 seconds to 10.6 seconds — an 11.9x improvement. Playwright dropped from 12.8 seconds to 1.47 seconds. And after opening the VS Code project, the time until the first error appeared fell from 17.5 seconds to under 1.3 seconds.The business impact is even more interesting. Slack reduced CI type-checking from roughly 7.5 minutes to 1.25 minutes and cut merge-queue time by 40%. Microsoft's News Services team estimates that adopting TypeScript 7 saves 400 hours of CI waiting time every month.Memory use dropped too. Building VS Code went from 5.2 GB to 4.2 GB, and Bluesky from 1.8 GB to 1.3 GB. On large CI instances, that stops being purely a speed story and starts affecting infrastructure cost.This isn't "the compiler got a bit quicker" anymore. It means fewer context switches, and a shorter loop between changing code and seeing the result.
Why Go?
Yes, Go compiles to native code — but it also gave the team a practical concurrency model and a better way to use multicore hardware.That is why the improvement is visible beyond tsc. Large projects load faster, while find-all-references, autocomplete, and diagnostics become more responsive. The new language service also uses the Language Server Protocol, making it easier to support across modern editors.
Upgrade, but test your toolchain first
TypeScript 7.0 does not yet ship with a stable programmatic compiler API; that is planned for 7.1. As a result, projects using Vue, Svelte, Astro, MDX, and some Angular workflows may still need TypeScript 6 for parts of their toolchain. Version 7 also enables strict mode by default and changes several tsconfig defaults.So the sensible first step isn't a company-wide migration. Try it in a separate branch and compare CI time, memory use, generated output, and tool compatibility.TypeScript 7 is a good reminder: sometimes the biggest performance gain doesn't come from one more optimization. It comes from replacing the foundation.