The biggest change in the language's history that changes nothing about the language
TypeScript 7.0 shipped on July 8th, and it's simultaneously one of the largest changes in the project's history and something that changes nothing about how you actually write code. The type system is identical. The syntax is identical. What's different is the thing underneath both of them: the compiler and language service, previously written in TypeScript itself and running on Node.js, has been completely ported to Go.
Microsoft's published benchmarks put full builds at roughly 8 to 12 times faster than TypeScript 6. The flagship number: type-checking the VS Code codebase — a genuinely large, real-world project — fell from 125.7 seconds on TypeScript 6 to 10.6 seconds on TypeScript 7, an 11.9x speedup at default settings.
Why a rewrite instead of incremental optimization
The project, internally codenamed "Project Corsa," was first announced back in March 2025, with the JavaScript-based codebase getting the retroactive nickname "Strada." The core insight driving the rewrite: native code and true multi-threaded compilation deliver a category of performance improvement that incremental optimization of a JavaScript-based compiler simply can't reach. Tools like esbuild and SWC had already proven this pattern for transpilation — but those tools strip types rather than checking them. TypeScript 7 is the first tool at this performance tier that keeps full type-checking intact while closing most of that speed gap.
The path from announcement to stable release took about sixteen months — a beta in April 2026, a release candidate on June 18th, and general availability on July 8th, following the RC by just under three weeks.
What's actually different for your workflow
Installation is now just npm install -D typescript — the native compiler ships under the standard latest tag rather than a separate preview package. tsc behaves the way it always has, just dramatically faster. Editor integration follows the same pattern: VS Code users get it through the TypeScript Native Preview extension, and Visual Studio 2026 enables it automatically in compatible workspaces.
The catch worth knowing before you migrate a large codebase: TypeScript 7.0 ships without a stable programmatic API. Microsoft has said 7.1 will deliver a new one, which means tools depending heavily on the compiler API — typescript-eslint, certain framework-specific type-checking layers — can't simply flip the switch yet. If your build pipeline leans on the programmatic API directly, this is worth checking before you commit to an upgrade.
Should you upgrade now?
For most day-to-day development — running tsc, getting IDE type-checking, catching errors before you ship — yes, and the upgrade path is close to a drop-in replacement since the type-checking semantics are preserved rather than reworked. For teams with tooling wired directly into the TypeScript compiler API, it's worth waiting for 7.1 or verifying your specific dependencies have caught up first.
Either way, the headline is genuinely simple: the tool that checks your code before you ship it just got roughly ten times faster, and you didn't have to change a single line to get there.
