On July 8th, 2026, Microsoft shipped TypeScript 7.0 — the first stable release built on a completely rewritten Go-based compiler. After over two years of development, the JavaScript-to-Go port is done, and the performance numbers are striking enough to change how teams think about type-checking at scale.
What Changed and Why It Matters
The TypeScript compiler has always been written in TypeScript itself, compiling down to JavaScript before it could run. That made for a tidy bootstrapping story, but JavaScript is single-threaded and garbage-collected — not ideal for a tool that needs to churn through millions of lines of code as fast as possible.
Go, the replacement language chosen by TypeScript's chief architect Anders Hejlsberg, offers native code speed, shared-memory multithreading, and syntax close enough to JavaScript that both codebases can be maintained in parallel. According to the official TypeScript blog announcement, full builds now typically run 8–12× faster than TypeScript 6, with memory usage roughly halved.
The benchmark that anchors the release: compiling VS Code — 2.3 million lines of TypeScript — went from 125 seconds under TS 6 to 10.6 seconds with TS 7. That's an 11.9× improvement. Sentry (1.9M lines) compiles in 15.7 seconds. Playwright (528K lines) in 1.47 seconds.
What This Means Day-to-Day
The speedup affects development workflows more than deployment. Developers using language server features — autocomplete, go-to-definition, inline error highlighting — will notice snappier responses on large projects. The bigger unlock is full project type-checking in CI: teams whose codebases were too large to run tsc --noEmit locally can now do it on a laptop.
Slack's engineering team is a cited example: previously they couldn't run a complete type-check on their own machine. With TypeScript 7, they can. That shifts type errors from a CI discovery to a local one, tightening the feedback loop considerably.
Compatibility and Migration
TypeScript 7 remains fully backward-compatible with TypeScript 6. The type system, compiler flags, and emitted JavaScript are unchanged — this is purely a performance rewrite, not a language change. Most projects can upgrade by bumping the version in package.json.
The one practical wrinkle: tooling that shells out to the tsc binary or uses the compiler API may need minor updates, since the internal runtime has switched from Node.js to a native Go binary. The TypeScript team has documented these edge cases in the release notes.
A New Foundation
TypeScript 7's Go port ends more than a decade of the compiler being written in itself. For a language now embedded in virtually every serious JavaScript project, an 11× improvement on release day signals there's more to come — and that Microsoft is treating TypeScript's build performance as a first-class concern going forward.