The compiler got rewritten in Go, and builds got an order of magnitude faster
TypeScript 7.0 reached general availability on 8 July 2026, and the headline change is not a new language feature but a new engine: the compiler itself has been ported from JavaScript to Go, Google's compiled programming language, while keeping its internal logic and structure intentionally close to the original so that type-checking behavior stays consistent with TypeScript 6. This was the project Microsoft had been developing under the codename "Project Corsa," publicly revealed back in March 2025.
The result, according to Microsoft's own testing across five real-world codebases, is a full type-check that runs somewhere between 7.7 and 11.9 times faster than before, alongside a meaningful drop in memory use. On the Visual Studio Code codebase itself, a full check fell from 125.7 seconds to 10.6 seconds, an 11.9x improvement, and tuning the new parallelism settings pushed that further down to 7.51 seconds. Other projects Microsoft benchmarked saw similar gains: Sentry's check time dropped from 139.8 to 15.7 seconds (8.9x), Bluesky from 24.3 to 2.8 seconds (8.7x), Playwright from 12.8 to 1.47 seconds (8.7x), and tldraw from 11.2 to 1.46 seconds (7.7x). Memory usage fell too, by 18 percent on the VS Code repository and by 6 to 26 percent across the other projects tested.
Why teams are already reporting real time savings
Those lab numbers are showing up in production reports. Slack says its continuous integration (CI) type-checking time dropped from roughly 7.5 minutes to 1.25 minutes, cutting close to 40 percent of the time its changes spend waiting in the merge queue. Microsoft's own News Services team reports saving around 400 engineering hours a month on CI builds. Canva says the time it takes to see the first error appear in its editor fell from 58 seconds to 4.8 seconds, and Vanta reports speedups of up to 9x on its larger projects. Editor responsiveness improved too: opening a file that contains errors in VS Code now takes under 1.3 seconds, down from 17.5 seconds.
None of this changes how a developer installs or runs the tool. It is still npm install -D typescript followed by npx tsc, plus new flags, --checkers, --builders, and --singleThreaded, for developers who want to tune how the compiler parallelizes work, and a watch mode rebuilt on a ported version of the Parcel file watcher.
What breaks, and who should wait
TypeScript 7.0 is not a drop-in replacement for every project. The strict compiler option now defaults to true and types now defaults to an empty array, meaning @types packages are no longer pulled in automatically. A set of long-deprecated options, including target: es5, baseUrl, moduleResolution: node, and the amd, umd, and systemjs module formats, now produce hard errors instead of warnings, and the downlevelIteration flag has been removed outright. A smaller but real gotcha: template literal types now treat Unicode code points as single units rather than splitting them into UTF-16 surrogate pairs, which can change how some string-manipulation types behave.
The bigger catch for the wider ecosystem is that TypeScript 7.0 ships without a stable programmatic compiler API; Microsoft is deferring that to version 7.1, expected roughly three to four months out. That matters because tools that hook directly into the compiler's internals, such as typescript-eslint, and frameworks with embedded-language tooling like Vue's Volar, Angular's template compiler, Svelte, Astro, and MDX, cannot fully move to 7.0 until that API lands. Microsoft's stopgap is a bridge package, @typescript/typescript6, which exposes a tsc6 binary and the old 6.0 API for tools that have not yet been ported.
Plain Node.js services, Next.js and React applications, and day-to-day editing in VS Code or Visual Studio are all clear to move to TypeScript 7.0 now, according to migration guidance published alongside the release. Microsoft's Daniel Rosenwasser, the project's principal product manager, has described TypeScript 6.0 as a deliberate bridge release between the 5.9 line and 7.0, and said the new compiler reliably surfaces the same errors 5.9 did; during the release candidate phase, Microsoft found only 74 error-reporting discrepancies against the old JavaScript-based compiler out of roughly 20,000 test cases.
What it means in practice
If your project is a typical application, framework-free library, or anything that only calls tsc from the command line or your editor, upgrading is likely to be a clean win: faster builds, faster editor feedback, and no code changes beyond fixing whatever strict: true newly flags. If your build depends on typescript-eslint, Vue, Angular, Svelte, Astro, or MDX tooling, hold off and track when each of those projects announces TypeScript 7.1 support, or use the tsc6 bridge binary in the meantime rather than blocking your whole toolchain on a single holdout dependency.
