TypeScript 7.0 went GA on July 8, 2026. Microsoft rewrote the entire compiler from TypeScript/JavaScript into Go — Project Corsa, a year-plus effort — and the numbers are real: VS Code’s 2.3-million-line codebase builds in 10.6 seconds instead of 125. Slack cut CI type-checking from 7.5 minutes to 1.25 minutes. The caveat matters: if your project uses Vue, Svelte, Astro, MDX, or Angular template type-checking, upgrading now will break your editor tooling. TypeScript 7.0 does not ship a stable programmatic API. That’s coming in 7.1.
The Benchmarks Are Not Marketing
Microsoft measured TypeScript 7 against real-world codebases, and the speedups are consistent. Native Go code plus shared-memory multithreading eliminates the JavaScript runtime overhead that has always been TypeScript’s ceiling.
| Project | TS 6 | TS 7 | Speedup |
|---|---|---|---|
| VS Code | 125.7s | 10.6s | 11.9x |
| Sentry | 139.8s | 15.7s | 8.9x |
| Bluesky | 24.3s | 2.8s | 8.7x |
| Playwright | 12.8s | 1.47s | 8.7x |
| tldraw | 11.2s | 1.46s | 7.7x |
Editor responsiveness improved just as dramatically. Opening a file with a type error in VS Code went from 17.5 seconds to under 1.3 seconds. Language server crashes dropped 60%; failing commands dropped 80%. This isn’t a minor release with a big version bump — the compiler is architecturally different. See the official TypeScript 7.0 announcement for the full benchmark methodology.
The type system itself is unchanged. Microsoft ported the logic rather than rewrote it, validating against 20,000 test cases. You get native speed without any type-checking behavior regression.
If You Use Vue, Svelte, Astro, or Angular: Wait for 7.1
Framework template type-checkers — Volar for Vue, MDX, and Astro; the Svelte language server; Angular’s template engine — embed TypeScript’s compiler directly via its programmatic API. TypeScript 7.0 doesn’t ship that API. Upgrading will break in-editor type errors, autocomplete, and template diagnostics for these frameworks. As TypeScript 7 Now Stable notes, these teams are blocked until the API ships.
Angular teams can run TypeScript 7’s tsc for CLI type checks — builds will be faster — but should keep TypeScript 6.0 for editor support until 7.1. Vue, Svelte, Astro, and MDX projects should stay on 6.0 entirely for now. The Angular team has a tracking issue open for 7.1 support.
TypeScript 7.1 is expected around October 2026. The stable programmatic API is its primary deliverable. Until then, if your project depends on these frameworks, hold off.
If you need TypeScript 7 features alongside API-dependent tooling, install both versions side-by-side:
npm install -D typescript
npm install -D typescript@npm:@typescript/typescript6
This gives you tsc on version 7 and tsc6 on version 6 for tools that still need the old API.
What Breaks When You Upgrade
TypeScript 6.0 (March 2026) was the bridge — it deprecated features that 7.0 removes as hard errors. If you skipped that cycle, you’ll hit these on the first tsc --noEmit run. The migration playbook in the RC post covers all of them in detail.
The one that catches most teams first: types now defaults to an empty array. Previously, TypeScript auto-discovered every @types/* package in your node_modules. Now you list them explicitly:
{
"compilerOptions": {
"types": ["node", "jest", "react"]
}
}
If you rely on @types/node globally — for Buffer, process, __dirname — you’ll hit errors immediately. Add it and move on.
Other hard errors worth knowing:
target: es5is gone — TypeScript 7 targets ES2015+ onlybaseUrlis removed — migrate topathsrelative to project rootmoduleResolution: nodeornode10are gone — usenodenextorbundlerstrict: falsecan no longer be set — strict mode is now permanentmoduledefaults toesnextinstead ofcommonjs— Node.js projects need explicit configuration
For most modern TypeScript projects on TS 5.x or 6.x, this is a morning’s work. Fix the config, fix the ambient types, run the build.
Squeeze More Speed Out of CI
TypeScript 7 defaults to 4 parallel type-checker workers. Bump to 8 with the --checkers flag:
tsc --checkers 8
On VS Code’s codebase this pushes the speedup from 11.9x to 16.7x. Monorepos with project references can parallelize those builds with --builders. Resource-constrained environments (Docker with limited CPUs, small CI runners) should use --singleThreaded to avoid contention.
The Upgrade Decision in Three Lines
If you’re on React, Next.js, or a plain TypeScript service: upgrade now. The build speed improvement is not marginal.
If you’re on Vue, Svelte, Astro, MDX, or Angular with template type-checking: wait for TypeScript 7.1, expected October 2026.
If you’re unsure, run tsc --noEmit after upgrading and read the errors. The migration is mechanical, not architectural — the type system did not change.













