Microsoft has shipped TypeScript 7.0, the first stable release to include a native compiler that delivers build-time speedups between 8x and 12x on full builds, according to an August 2026 announcement from the company. The new toolset represents a complete rewrite of the TypeScript compiler from TypeScript into Go, a project that began as an experimental port announced in March 2025 and reached more than 8.5 million weekly downloads as a preview package before merging into the standard release.

Microsoft published benchmark data showing dramatic performance gains across real-world codebases. A full build of the VS Code source dropped from 125.7 seconds on TypeScript 6 to 10.6 seconds on version 7.0, an 11.9x improvement, while total memory consumption fell by roughly 18 percent. The Sentry codebase saw a reduction from 139.8 seconds to 15.7 seconds, an 8.9x speedup, and Bluesky's build time shrank from 24.3 seconds to 2.8 seconds, representing an 8.7x gain. Playwright went from 12.8 seconds to 1.47 seconds (8.7x faster), and Tldraw improved from 11.2 seconds to 1.46 seconds, a 7.7x boost. Editor responsiveness also improved because the new tooling uses the Language Server Protocol and runs on multiple threads—opening a file with an error in the VS Code codebase previously required about 17.5 seconds but now takes under 1.3 seconds. Early adopters reported similar results: Slack engineers said CI type-checking time fell from approximately 7.5 minutes to 1.25 minutes, and Vanta noted that "everything is so, so much faster now."

The release ships without a stable programmatic API, which the team expects to deliver in version 7.1, meaning tools like typescript-eslint and framework tooling for Vue, Svelte, Astro, MDX, and Angular can't use the new compiler yet. Microsoft published a compatibility package, @typescript/typescript6, that provides a tsc6 binary and re-exports the 6.0 API so existing tooling continues to work through npm aliases. TypeScript 7.0 also converts the deprecations from version 6.0 into hard errors, with strict and esnext now set as defaults, so the team recommends adopting TypeScript 6.0 first to ease the transition. Developers can adjust parallelism using the new --checkers and --builders flags or disable it entirely with --singleThreaded for environments with limited resources.

Unlike faster alternatives such as esbuild, swc, and Biome—which strip or convert types without validating them—TypeScript 7.0 maintains full type-checking while narrowing much of the performance difference. The approach matters for large teams that depend on type safety to catch errors before code reaches production. By keeping the validation step intact and speeding it up through parallelism and a compiled binary rather than an interpreted runtime, the new compiler offers a middle path: developers get the safety guarantees they're used to without waiting minutes for CI pipelines to finish. That trade-off explains why early testers saw such steep drops in continuous integration times—the bottleneck wasn't just build speed but the cost of running full checks on every commit.

The team says feature development resumes now that the port has shipped, with new releases expected every three to four months and version 7.1 focused on the programmatic API the broader ecosystem is waiting for. TypeScript remains open-source under the Apache 2.0 license, and the migration path through compatibility packages means projects can upgrade incrementally rather than all at once. For teams running large codebases or frequent CI checks, the speedup turns what used to be a coffee break into a few seconds—and that changes how fast code can move.