arenru
July 21, 2026#typescript#javascript#tooling#compiler#performanceavailable in Arabicavailable in Russian

TypeScript 7: A Native Compiler, 10× Faster

TypeScript 7.0 hit GA on July 8, 2026: a native compiler rewritten in Go that builds 10× faster. What changed, the caveats, and how to upgrade safely.

TypeScript 7: A Native Compiler, 10× Faster

On July 8, 2026, TypeScript 7.0 reached general availability and is production-ready. This is more than a version bump: it's the first full rewrite of the TypeScript compiler from JavaScript to Go. The team calls it "a 10× faster native port," and benchmarks from real projects back that up.

The problem that kept growing

On small projects, tsc speed barely registers. But as a codebase grows, type-checking becomes a visible bottleneck: builds that stretch into tens of seconds, editors that lag on autocomplete, large files that make you wait before you can work. The deeper cost is the broken feedback loop — the core of any healthy development process. A few seconds of waiting, multiplied across hundreds of checks a day, turns into lost time and scattered focus.

What actually changed

Instead of incremental tweaks, the team ported the entire compiler codebase to Go, keeping the same structure and logic so output stays compatible with earlier versions. The result is a documented leap on open-source projects:

  • VS Code: 125.7s → 10.6s — 11.9× faster
  • Sentry: 139.8s → 15.7s — 8.9× faster
  • Playwright: 12.8s → 1.47s — 8.7× faster

And it isn't just builds. Opening a file in the editor dropped from about 17.5 seconds to under 1.3, memory use improved by 6–26%, and failing language-server commands fell by over 80%. Type-checking now parallelizes across workers, and --watch mode was rebuilt from the ground up.

A practical example

Installation is unchanged:

npm install -D typescript
tsc --checkers 8 # parallelize type-checking across 8 workers

For a side-by-side TypeScript 6 during a gradual migration:

npm install -D @typescript/typescript6

Mind your config — several defaults changed in 7.0:

{
"compilerOptions": {
"strict": true, // now the default
"module": "esnext", // new default
"types": [] // no longer auto-includes every @types package
}
}

Real-world caveats

The upgrade rewards planning over a blind version bump:

  • No programmatic API in 7.0 — it's expected in 7.1 (around October 2026). So tools like typescript-eslint stay on TypeScript 6.0 for now.
  • Template frameworks wait their turn: Vue, Svelte, Angular, Astro, and MDX rely on Volar, which embeds the compiler directly; they won't get the editor speedups until the stable API ships.
  • Migration path: moving from 5.x goes through 6.0 first to clear deprecation warnings, since 7.0 turns them into hard errors. Legacy options like target: es5, downlevelIteration, and AMD/UMD modules were removed.

The takeaway

Speed here isn't a luxury; it's a shorter feedback loop and a firmer foundation for automation and agentic development, which lean on fast, repeated type-checking. Faster tools multiply a developer's capacity rather than replace it — and that's exactly where the platform is heading in 2026, much as we saw with the new QUERY HTTP method. Plan the upgrade today, and you build on faster, clearer ground tomorrow.

Primary source: the official TypeScript 7.0 announcement.