TypeScript 7.0 builds code 10x faster — Vue, Svelte, and Angular have to wait

The TypeScript compiler inside VS Code used to spend 125 seconds checking a fresh copy of the editor’s own codebase. TypeScript 7.0 does the same job in 10.6 seconds. Microsoft didn’t optimize the old code — it ported the entire compiler runtime from JavaScript to Go, unlocking multi-core parallelism that a JavaScript engine can’t provide.

The port is not a ground-up rewrite. Microsoft’s engineers described the type-checking logic as structurally identical to TypeScript 6.0 — the same rules, the same behavior, translated to a language that can spread work across CPU cores. The team chose Go because the original function-heavy JavaScript codebase mapped to Go idioms nearly one-to-one. The new runtime also introduces flags for explicit parallelism control: passing –checkers 8 on a modern workstation pushes the VS Code build to a 16.7x improvement over TypeScript 6. Slack’s CI type-checking dropped from 7.5 minutes to 1.25. Bluesky’s build went from 24.3 seconds to 2.8. The pattern holds across codebases: the gains compound as project size grows, because the ceiling is now hardware, not runtime.

TypeScript 7.0 ships without a public programmatic API — the interface build tools use when they call the compiler from inside their own code. Every major web framework’s template type-checker depends on it. Vue’s Volar tooling, Svelte’s language service, MDX, Angular’s template checker: none of them work against TypeScript 7.0. Tools like ts-morph and ts-jest, which expose TypeScript compiler internals for refactoring and testing, are also broken. Microsoft has confirmed the replacement API is planned for TypeScript 7.1, expected in October. Projects using any of those frameworks or tools should not upgrade yet.

Older project configurations face a separate set of hard stops. TypeScript 7.0 turns options that version 6.0 deprecated into hard build errors: ES5 compilation targets, AMD and SystemJS module formats, classic module resolution, and the assert keyword on import statements all cause the build to fail outright. The new default tsconfig.json no longer auto-loads @types packages, meaning projects that relied on ambient type discovery without explicitly declaring their type dependencies will fail silently at import time. Microsoft provides a typescript@npm:@typescript/typescript6 compatibility shim 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. Editor support tracks the same split: VS Code has a dedicated TypeScript 7 extension available now, and the built-in support is completing its migration to the Language Server Protocol, replacing the older TSServer design. WebStorm and other editors that also depended on TSServer are still working through that transition.

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.

Tags: microsoft, programming, Go, TypeScript