TypeScript 7 vs tsrs: The Real Battle of Native Compilers

6 min read

TypeScript 7 (Go) vs tsrs (Rust): which native compiler to migrate to in production today? Benchmarks, limitations, and verdict by use case.

Close-up of a mechanical keyboard in a dark office with a blurred screen in the background

Microsoft rewrote the TypeScript compiler in Go. Cloudflare just rewrote it in Rust, with help from an LLM. Both projects target the same goal, killing the slowness of the historical compiler written in JavaScript, but they're not at the same stage, and picking the wrong one today can break your CI without warning.

We'll compare the two: what they promise, what they've already delivered, and which one has a place in a production Next.js stack this year.

TypeScript 7, Microsoft's Official Bet

The TypeScript team announced TypeScript 7.0 on July 8, 2026, a few months after version 6.0 launched on March 23. The change is far from cosmetic: the compiler, checker, and language server are now a native binary written in Go, plus the old JavaScript implementation that used to run on Node.

Microsoft, TypeScript team, July 8, 2026 "a 10x faster native port of TypeScript"

Ten times faster, according to the Tech Insider report on Microsoft's announcement. It's the number bouncing around everywhere. It deserves some nuance: the real gain depends heavily on project size and the number of .d.ts files loaded at startup. On a medium-sized Next.js monorepo, most of the gain shows up on a full tsc --noEmit run, far less on incremental watch mode, which was already optimized.

Microsoft also released a beta of TypeScript 7.1 on October 20, 2026, a steady release cadence that shows the project isn't just a side bet.

The choice of Go surprised parts of the community. A Hacker News comment summed it up well: some internal Microsoft teams are already moving .NET and TypeScript code to Rust elsewhere in the company. So the choice of Go for the official compiler isn't an obvious technical necessity, it's a team trade-off, not law.

Tsrs, Cloudflare's Risky Bet

Three months later, Cloudflare and VoidZero publish their own answer: tsrs, a port of the TypeScript compiler, checker, and language server to Rust. One notable detail: a good chunk of the port was done with help from an LLM, a detail that sparked vigorous discussion on Hacker News in early October.

Cloudflare, official blog, October 20, 2026 "The current build remains experimental. The build lacks watch mode and a language server. Unsupported flags include --init and --showConfig. Diagnostic ordering can differ from tsc"

It's spelled out plainly on Cloudflare's blog. No watch mode. No working language server. Missing flags. And error diagnostic ordering that differs from the original tsc, which means your CI scripts that parse the compiler's text output can silently go wrong.

The choice of Rust is no accident for Cloudflare: the Workers ecosystem already runs heavily on that language, and a native TypeScript compiler in Rust integrates more cleanly into their in-house toolchain.

Migrating a TypeScript stack this year? Let's talk about your build pipeline.

The Table That Settles It: Speed, Maturity, Compatibility

CriterionTypeScript 7 (Go, Microsoft)tsrs (Rust, Cloudflare/VoidZero)
Announcement dateJuly 8, 2026 (v7.0), beta v7.1 Oct. 20, 2026~October 20, 2026
StatusStable release + active betaExperimental, pre-alpha
Watch modeYesNo
Language serverYesNo
--init / --showConfig flagsSupportedNot supported
Diagnostic orderingIdentical to historical tscMay differ from tsc
Announced speed gain"10x" (Microsoft announcement)Not publicly quantified
EditorMicrosoft (language owner)Cloudflare / VoidZero (third party)

A table that speaks for itself: only one of these two projects can reasonably replace your tsc in CI today.

Which One to Adopt Now, Case by Case

If your team has fewer than 10 developers and TypeScript build isn't your main bottleneck, don't migrate anything yet. The real gain on a reasonably sized Next.js project stays modest as long as your CI pipeline isn't burning several minutes on typecheck alone.

For large monorepos, past a few hundred thousand lines of code, with typecheck exceeding 3, 4 minutes in CI, TypeScript 7 deserves a test run in a staging environment. It's an official product, maintained by the team that owns the language, with a clear release trajectory.

tsrs, meanwhile, has no place in production. No working language server means no proper autocomplete in your editor. For a product team shipping daily, that's a dealbreaker. Keep an eye on it if you closely follow the Cloudflare Workers ecosystem, nothing more for now.

Common Pitfall: migrating to TypeScript 7 by flipping the whole monorepo at once without first checking ESLint plugins and build tools (Webpack, Vite) that sometimes rely on undocumented internal APIs from the historical JavaScript implementation.

Conclusion

Three takeaways. First, TypeScript 7 is a stable product backed by the language's owner, it's the serious option for 2026. Second, tsrs is an interesting prototype but not viable in production while the language server is missing. Finally, compilation speed is only a real problem for large monorepos: don't migrate for hype.

Working on a TypeScript stack that's starting to slow down your CI? That's exactly the kind of project we tackle in custom web development at fstck, get in touch to discuss.

Frequently Asked Questions

Is TypeScript 7 compatible with my existing TypeScript 6 code?

In the vast majority of cases, yes, the Go port aims for functional compatibility with the historical compiler. Still, test your advanced tsconfig.json configurations and build plugins before switching over a production pipeline.

Should I use tsrs on a real project today?

No. Cloudflare describes it themselves as experimental, without watch mode or a working language server. It's a project to follow, not a tool to deploy.

Does TypeScript 7 replace Node.js in the build chain?

No, TypeScript 7 replaces the JavaScript implementation of the compiler with a Go binary, but your application runtime (Node.js, Bun, Deno) is unaffected. Only the typecheck tool changes.

Why did Microsoft pick Go over Rust for its own compiler?

The TypeScript team hasn't published detailed technical reasoning for that choice. Other internal Microsoft teams use Rust on other projects elsewhere, which shows this is a team trade-off rather than a company-wide preference.

What performance gain should I realistically expect on a Next.js project?

The "10x" figure Microsoft communicated applies mostly to full typecheck on large projects. On a medium-sized Next.js monorepo with watch mode already active, the day-to-day difference is more modest.

Équipe Fullstack
Follow us on LinkedIn →

Let's talk about your project

Got a project in the works, a bold idea?
Let's meet and talk about it.

Contact us
→