TypeScript 7.0 ships native Go compiler, cuts build times 10x

Microsoft shipped TypeScript 7.0 on August 3, the first stable release to include the native Go-based compiler the team has been building since March 2025. The new toolchain delivers 8x to 12x faster full builds on real codebases, with the VS Code source compiling in 10.6 seconds versus 125.7 seconds on TypeScript 6.

The port began as an experiment and shipped as the @typescript/native-preview package, which hit 8.5 million weekly downloads before graduation. With 7.0, nightly builds move back under the standard typescript package on npm's next tag. Installation is the usual one-liner: npm install -D typescript.

How fast is TypeScript 7.0 in practice?

Microsoft published benchmarks against production codebases. Sentry's build dropped from 139.8 seconds to 15.7 seconds, an 8.9x gain. Bluesky saw 8.7x, going from 24.3 seconds to 2.8 seconds. Playwright and tldraw both clocked around 7.7x to 8.7x improvements. Memory consumption fell roughly 18 percent across the board.

Editor responsiveness improved even more dramatically. The new tooling is built on the Language Server Protocol and uses multiple threads. Opening a file with an error in the VS Code codebase previously took about 17.5 seconds. It now takes under 1.3 seconds.

Teams testing early releases reported similar gains. Slack engineers said CI type-checking fell from about 7.5 minutes to 1.25 minutes. Vanta's team was blunt about the impact.

“Our tsgo adoption at Vanta has been pretty high-impact. Everything is so, so much faster now.”

— Vanta engineering team

What breaks in TypeScript 7.0?

The release ships without a stable programmatic API. That means tools like typescript-eslint and framework tooling for Vue, Svelte, Astro, MDX, and Angular cannot use the native compiler yet. Microsoft expects the API to land in version 7.1.

Projects using webpack loaders face the same wait. As one commenter on the TypeScript blog put it: "Most of them use webpack, and there seems to be no API surface in the 7.0 release for webpack loaders to utilize. I'll sadly have to wait for 7.1."

Microsoft published a compatibility package, @typescript/typescript6, that provides a tsc6 binary and re-exports the 6.0 API. Teams can run both compilers side by side during migration, wired through npm aliases.

TypeScript 7.0 also turns 6.0's deprecations into hard errors. The defaults shift to strict and esnext. Microsoft recommends adopting TypeScript 6.0 first to identify and fix breaking changes before jumping to 7.0.

How does this compare to esbuild or swc?

Unlike esbuild, swc, and Biome, which strip or transpile types without checking them, TypeScript 7.0 keeps full type-checking while closing much of the speed gap. For teams that need type safety, not just fast transpilation, this is the difference that matters.

Parallelism can be tuned with the new --checkers and --builders flags, or disabled entirely with --singleThreaded for constrained CI environments. The behavioral differences from 6.0 are tracked in the project's CHANGES.md file.

What comes next?

Microsoft says feature work resumes now that the port has shipped. New releases are expected every three to four months, with 7.1 focused on the programmatic API the wider ecosystem needs. Once that lands, the ecosystem can migrate in earnest.

TypeScript remains open source under the Apache 2.0 license. The question for engineering managers: how much CI time are you burning today, and does the migration cost justify a 7.1 wait or a staged 7.0 rollout for pure tsc workflows?

Source: InfoQ