TypeScript 7.0 Is Officially Here: What Changed and How to Upgrade

Something that's been talked about for well over a year finally has a release date behind it instead of a rumor attached to it. On July 8, 2026, Microsoft officially shipped TypeScript 7.0 — the native, Go-based rewrite of its compiler — after a release candidate that had been circulating since June. No more caveats. No more "coming soon." It's out, and it's meant for production.

Here's what's actually in it.

What's Different Under the Hood

The core change is straightforward to state and took over a year to execute: TypeScript's compiler no longer runs on top of JavaScript. It's native code now, written in Go. Microsoft's own figures put full builds somewhere between 8x and 12x faster than the previous JavaScript-based compiler, depending on the size and shape of the project.

Two things are doing most of the work here. First, native code simply doesn't carry the overhead a JavaScript-hosted compiler does — that's a straightforward performance win, not a clever trick. Second, and more interesting, is shared memory multithreading, which lets the compiler actually parallelize work that used to be forced through a single thread. Layer a handful of smaller optimizations on top of those two changes and you land on the headline number.

What's worth noting is the discipline behind the rewrite. Microsoft didn't use the move to Go as an excuse to redesign TypeScript's behavior. The port was done specifically to preserve the structure and logic of the original codebase, so that the new compiler produces results consistent with the old one. That's a much harder constraint to work under than a from-scratch rebuild, and it's the reason existing codebases should be able to move over without their type-checking behavior shifting underneath them.

Installing It

There's no special installation ceremony:

npm install -D typescript

That's the whole story. It replaces the previous package the same way any major version bump would.

What Happens to Tooling Built on the Old API

The real logistical question for teams isn't "how do I install this" — it's "what happens to everything I've built against TypeScript's compiler API." TypeScript 7.0 ships without its own full programmatic API; that's slated for TypeScript 7.1. In the meantime, linters, build plugins, and anything else wired directly into the compiler's internals need a bridge.

Microsoft's answer is a compatibility package: @typescript/typescript6. It installs an executable called tsc6, which re-exports the TypeScript 6.0 API. That means TypeScript 7.0 can keep its own tsc binary for new work, while anything still depending on the TypeScript 6.0 API gets pointed at tsc6 instead. Nobody has to migrate their entire toolchain overnight — both versions run side by side, and you move at your own pace.

What Comes Next

Microsoft is calling this rewrite a major milestone for the project, and it's fair to say it's been the primary focus of the TypeScript team for more than a year — a long stretch to have your core engineers heads-down on a migration instead of new features. With the rewrite shipped, the team says it's returning to the more familiar rhythm of language work: new features, ergonomic improvements, continued performance tuning, and that full programmatic API for the broader ecosystem to build on top of.

On cadence, Microsoft isn't signaling any change from the pattern that existed before this whole project started: expect new releases roughly every three to four months going forward.

The Bottom Line

A compiler rewrite doesn't come with screenshots worth posting, but it's the kind of change that quietly determines whether your builds keep you in flow or keep interrupting it. TypeScript 7.0 spent over a year getting stress-tested internally before this release, which is about as much validation as any infrastructure change gets before hitting the public. If you're on TypeScript 6 now, this is the moment to start testing your own build times against it — not someone else's numbers, yours.