- TypeScript 7.0 rewrites the compiler in Go, achieving 10–12x performance improvements over version 6.
- The new version lacks a public programmatic API, breaking tools like Volar, ts-jest, and framework template checkers until 7.1 arrives.
- Projects using deprecated options (ES5, AMD, classic module resolution) will fail; a compatibility shim is available.
- Editor support moves to the Language Server Protocol, with a dedicated VS Code extension already available.
Microsoft has finally released TypeScript 7.0, and it’s a big deal – not because of new language features, but because the entire compiler has been rewritten in Go. The result? A compiler that’s up to 12 times faster than its predecessor. The move addresses a long-standing pain point for developers working on large codebases: the wait for type-checking and compilation.
The team decided to port the entire compiler runtime from JavaScript to Go after years of struggling with performance and memory issues. JavaScript, originally designed for UI and browser interactions, simply wasn’t built for compute-intensive workloads like a compiler. By moving to Go, Microsoft unlocked shared-memory concurrency, allowing the compiler to spread work across multiple CPU cores – something a single-threaded JavaScript engine could never do.
Performance Numbers That Speak for Themselves
The benchmarks are striking. Visual Studio Code’s own build dropped from 125 seconds to just 10.6 seconds – an 11.9x improvement. Slack’s CI type-checking went from 7.5 minutes down to 1.25 minutes, and Bluesky’s build shrank from 24.3 seconds to 2.8 seconds. On a 16-core machine, the default configuration uses four parallel type checkers, but cranking that up to 12 checkers yields a 12x speedup. The gains scale with project size because the bottleneck is now hardware, not the runtime.
Anders Hejlsberg, Microsoft Technical Fellow, demonstrated the difference live: opening a file with an error in the editor took 17.5 seconds with TypeScript 6, but only 1.3 seconds with TypeScript 7. The language service itself has been rewritten to use the Language Server Protocol (LSP), making it easier to integrate with other editors and AI tools. VS Code already has a dedicated TypeScript 7 extension, and the built-in support is migrating away from the old TSServer design.
What Breaks and What Doesn’t
Despite the performance gains, TypeScript 7.0 ships without a public programmatic API. That means every major web framework’s template type-checker – Vue’s Volar, Svelte’s language service, Angular’s template checker, MDX – is incompatible. Tools like ts-morph and ts-jest, which rely on compiler internals, also break. Microsoft has confirmed a replacement API will arrive in TypeScript 7.1, expected in October 2026. Until then, projects using those frameworks should stick with TypeScript 6.0.x.
Older project configurations face hard stops. Options that were deprecated in version 6 now cause build failures: ES5 compilation targets, AMD and SystemJS module formats, classic module resolution, and the assert keyword on imports all fail outright. The new default tsconfig.json no longer auto-loads @types packages, so projects relying on ambient type discovery without explicit type dependencies will fail silently. Microsoft provides a compatibility shim (typescript@npm:@typescript/typescript6) for projects that need to keep TS6 tooling running alongside the new compiler.
Projects that clear those hurdles – plain Node.js or Deno applications, browser apps not built on a framework template system, and libraries without programmatic API dependencies – can upgrade with a single package.json change. The payoff is real: Slack reported 40% less merge queue time, and Microsoft News Services estimates 400 hours saved per month just waiting on pipelines.
TypeScript 7.1, currently targeted for October 2026, will ship the new compiler API that Vue, Svelte, Angular, and MDX tooling need before they can migrate. When it arrives, the performance gains from the 15-month Go port will reach the full ecosystem. Until then, the project pages for Volar, SvelteKit, and Angular recommend holding at TypeScript 6.0.x. For everyone else, the upgrade is straightforward – and the time saved is anything but trivial.
