Inside TypeScript 7's Go Rewrite: Speed Gains Without Code Changes

The compiler now runs on a Go-based engine, your existing code needs no changes, and build times have dropped dramatically

Major tooling updates that only arrive once every few years tend to reshape your daily workflow, and TypeScript 7 fits that pattern. Microsoft rebuilt the compiler for substantially better performance — full builds run 8 to 12 times faster — without requiring any changes to the language features you already use.

What Actually Shipped

TypeScript 7 arrived on July 8, 2026, replacing the JavaScript-based compiler with a native Go implementation built under the internal effort known as Project Corsa. It's worth stressing that this is a faithful port rather than a redesign: the same type-checking logic and language semantics were translated line by line, so your .ts files behave exactly as they did before. The part that changed is the underlying engine executing that logic, not the logic itself.

According to Microsoft's internal benchmarks, run against the VS Code codebase itself, project load times fell from close to a minute down to roughly ten seconds. That's the headline result. In practical terms, the delay you used to experience running tsc --watch after switching branches largely goes away.

Why It's So Much Faster

Two architectural changes account for most of the speed gain.

• Compiled native code instead of running through Node.js and the V8 engine
• Shared-memory parallelism, letting parsing, type-checking, and code emission run simultaneously across multiple CPU cores

The release also introduces new flags, --checkers and --builders, which let you control how many parallel worker threads handle type-checking and project-reference builds. Watch mode has been reworked too, borrowing a Go-based file watcher originally developed for Parcel, and it now performs incremental rebuilds noticeably faster on large monorepos.

How to Actually Upgrade

Installing the new compiler works exactly the way it always has:

npm install -D typescript
npx tsc --version
# TypeScript 7.0

There's no configuration migration to perform, no codemods to run, and no breaking syntax changes to account for. If your team had already adopted the @typescript/native-preview package during the release-candidate phase, that functionality — built around the tsgo binary — has been folded back into the standard typescript package, accessible through the next distribution tag.

One caution is worth flagging: the programmatic compiler API hasn't fully stabilized yet. If your build pipeline, ESLint configuration, or custom tooling relies on the TypeScript API directly rather than just invoking tsc, avoid writing new code against interfaces like createProgram for now. Teams in that situation should hold off on a full cutover until version 7.1 ships, since that release is expected to close the gaps that opened up during last year's transition work.

What This Means for React and Next.js Projects

Because so much framework tooling is built on top of the TypeScript compiler, that tooling inherits the performance improvements automatically. Build-time type-checking in Next.js, editor IntelliSense responsiveness in large component libraries built with Redux or Tailwind, and type-checking across monorepo project references all get faster without any code changes on your part. For teams that have been putting off enabling strict: true because full-project type-checking felt too slow to justify, this is a reasonable moment to reconsider — the computational cost of that decision just dropped by an order of magnitude.

Key Takeaways

• TypeScript 7 rewrites the compiler, not the language — your code type-checks the same way, just on a new Go-based engine.
• Full builds are 8 to 12 times faster, and editor project loading is dramatically quicker as well.
• Upgrading is as simple as running npm install, but avoid depending on the programmatic API for custom tooling until version 7.1 lands.
• Framework-based projects, including React and Next.js apps, get the speedup automatically with no configuration changes required.

If build times were the reason you avoided turning on strict type-checking, that excuse no longer holds. Install the new version, run your existing test suite, and watch your CI pipeline times drop.