TypeScript 7.0 Is Out: The Go-Native Compiler Promises Builds Up to 10x Faster
On July 8, 2026, Microsoft released the stable build of TypeScript 7.0, one of the most far-reaching changes in the language's history. This is not about adding a few utility types or new syntax — it replaces the very core of the tool. The compiler, previously written in TypeScript itself, has been rewritten in Go. The headline result, now measured on real projects, is type-checking that is "roughly ten times faster." For teams living day to day with build times and editor latency that had become painful on large codebases, this is the most concrete piece of news of the year.
A project codenamed "Corsa," led by Anders Hejlsberg
The story goes back to spring 2025, when Microsoft revealed its plan to port TypeScript to a native compiled language under the codename "Corsa." Leading the effort is Anders Hejlsberg, TypeScript's original architect and the designer of C# and, before that, Turbo Pascal. The choice of Go was deliberate: its memory management, native concurrency and structural closeness to the existing code enabled a methodical port rather than a risky rewrite. The team stressed this point repeatedly — the type-checking logic remains structurally identical to version 6, which sharply limits the risk of behavioral regressions.
After an initial public preview, an official beta on April 21, 2026 and a release candidate in mid-June, the stable 7.0 landed in early July. Along the way, the compiler was battle-tested on multi-million-line codebases at Microsoft, but also at Bloomberg, Canva, Figma, Google, Slack and Vercel, who reported as early as the beta that they were "shaving off a majority of their build times." The source code for the new compiler is open and available in the microsoft/typescript-go repository on GitHub.
Numbers that speak for themselves
The most dramatic gain is in full type-checking. On the Visual Studio Code codebase — a reference every developer knows — the type-check time drops from 125.7 seconds on TypeScript 6 to 10.6 seconds on TypeScript 7, an almost twelvefold speedup. On the Sentry project it falls from 139.8 to 15.7 seconds. These are not cherry-picked outliers: they mirror a trend seen across most large repositories, with a speedup factor hovering around ten depending on the nature of the project.
Memory consumption drops too, in a range of 6 to 26% depending on the project. That is less spectacular than a tenfold gain, but far from trivial on a continuous-integration pipeline running several checks in parallel. The new compiler is also parallel by design: a --checkers flag (four workers by default) spreads type-checking across cores, while a --builders flag speeds up monorepos made of many sub-projects. A --singleThreaded mode remains available for debugging.
The editor gets faster, too
Cutting build times is useful, but that is not where most of the daily comfort lives. The real turning point is the language server — the piece that powers autocompletion, type hovers, "go to definition" and error reporting right inside the editor. By porting that layer to Go, TypeScript 7 slashes the initial project load time and interaction latency. In practice, on a large codebase, opening a file and getting relevant suggestions no longer comes with several seconds of waiting, which changes the very nature of the work. During the preview phase these capabilities shipped through the @typescript/native-preview package and a dedicated VS Code extension; with the stable release, the standard tsc binary is now the native compiler, with no separate tsgo command to invoke.
A major version that forces a few breaks
Moving to TypeScript 7 is not entirely painless, and that is by design. The team used this major version to clean up inherited settings. strict mode is now on by default, type auto-discovery (types: []) is no longer implicit, and the source root (rootDir) must be configured explicitly. On compilation targets, ES5 support is gone, as are the legacy AMD, UMD and SystemJS module formats and "classic" module resolution. In other words, modern projects already in strict mode and targeting current ES modules will migrate with almost no effort, while older codebases should plan a focused upgrade. It is a reasonable trade-off: the performance of a native compiler is paid for by dropping a long legacy of compatibility that few teams still rely on.
Why this is genuinely good news for teams
It is tempting to reduce this announcement to an engineering feat reserved for maintainers of very large codebases. That would miss the point. Build times and editor latency are an invisible tax levied on every developer, at every moment of the day. When a full type-check drops from two minutes to ten seconds, it is not just a benchmark table that improves: it is the developer's feedback loop that tightens, the CI that costs less machine time, and a daily friction that disappears. For an agency like ours, which builds its applications in TypeScript on projects running under Next.js or Astro, this kind of gain translates directly into shorter delivery cycles and a restored quality of daily work.
The shift also confirms a deeper trend in web tooling: after Tailwind's Oxide engine written in Rust, after JavaScript runtimes betting on systems languages, it is now the TypeScript compiler's turn to leave the interpreted world for raw speed. The choice of Go over Rust sparked lively debate in the community, with the team justifying its decision by the memory model's closeness to the original code and the smoothness of the port. Whichever side you take, the message is clear: in 2026, tooling performance is no longer a detail but a first-class design criterion.
For teams already up to date and on a modern configuration, the recommendation is simple: try TypeScript 7 on a dedicated branch as soon as possible, because the return on investment is immediate and the regression risk is low. For older projects, it is a good opportunity to plan a modernization that, beyond speed, will improve type rigor. In both cases the trajectory is now set: the historical JavaScript compiler is living its final months of service, and the entire ecosystem will progressively move to this native foundation. Official documentation and migration guides are available on the TypeScript website.
