TypeScript 7.0 Ships as General Availability, With Microsoft Citing 8x to 12x Faster Builds From Its Native Go Compiler
Microsoft shipped TypeScript 7.0 as generally available on July 8, 2026, moving the compiler and language service to a native Go port that Microsoft says is typically 8x to 12x faster on full builds.
Overview
Microsoft shipped TypeScript 7.0 as generally available on July 8, 2026, according to the TypeScript team’s announcement, which opens: “Today we are proud to announce the availability of TypeScript 7, a 10x faster native port of TypeScript!” The release replaces the compiler and language service — previously written in TypeScript itself and run on the V8 JavaScript engine — with a full native port written in Go, a shift The Machine Herald previously reported when the project reached beta in May. The Register opened its coverage: “The Microsoft-led TypeScript 7.0 features an order-of-magnitude speed boost, a victory not only for TypeScript itself but also for Go, the programming language used to completely rewrite the web staple’s compiler.”
What We Know
GA follows a Release Candidate that Microsoft’s TypeScript team, led by Principal Product Manager Daniel Rosenwasser, announced on June 18, 2026 — meaning the stable release landed just under three weeks after the RC. A GitHub release for the typescript-go repository, tagged typescript/v7.0.2 and timestamped July 8 at 15:58, links directly back to the official announcement, corroborating the ship date.
On performance, Microsoft states that “TypeScript 7 brings native code speed, shared memory multithreading, and a number of new optimizations that typically yield speedups between 8x and 12x on full builds,” according to the official announcement — a quote The Register independently reproduced and attributed to Rosenwasser as well. Microsoft’s published benchmark table shows the VS Code codebase compiling in 10.6 seconds on TypeScript 7, down from 125.7 seconds on TypeScript 6, a 11.9x improvement; Sentry’s codebase went from 139.8 seconds to 15.7 seconds (8.9x); Bluesky from 24.3 seconds to 2.8 seconds (8.7x); and Playwright from 12.8 seconds to 1.47 seconds (8.7x), per the DevBlog post. The same post reports memory-usage reductions across those projects ranging from 6% to 26%, with the VS Code codebase’s peak memory falling from 5.2GB to 4.2GB, an 18% drop.
Editor responsiveness also improved: Microsoft says that “opening a file with an error in the VS Code codebase would previously take about 17.5 seconds from the time you opened the editor to the time you saw the first error. With TypeScript 7, it’s under 1.3 seconds – over 13x faster,” according to the announcement. Microsoft also reports the new language server fails 80% fewer commands and crashes 60% less often than TypeScript 6.0.
Companies that tested pre-release builds include Slack, Vanta, Canva, Figma, Google, Bloomberg, Linear, and Notion, according to Microsoft. Microsoft writes that “Slack engineers have told us that TypeScript 7 eliminated 40% of their merge queue time and brought type-checking time in CI from about 7.5 minutes to 1.25 minutes.” The Register frames the result plainly: “With TypeScript 7, full type checks can be done by the developer again at Slack.” Microsoft also reports that Vanta saw speedups of up to 9x on major projects, Canva’s time-to-first-error fell from 58 seconds to 4.8 seconds, and Microsoft’s own News Services team saved 400 hours per month of CI build time.
GA ships under npm’s normal latest tag, so running npm install -D typescript now installs version 7.0, per the announcement. Nightly builds move from the beta-era @typescript/native-preview package — which Microsoft says had reached 8.5 million weekly downloads — to typescript@next. For teams not yet ready to move, Microsoft published a new compatibility package, @typescript/typescript6. As the DevBlog post explains: “This package provides an executable named tsc6, so that if needed, you can install TypeScript 7.0 (which ships its own tsc binary) side-by-side without naming conflicts.”
The release adds new CLI flags for controlling the compiler’s multithreading: --checkers (which defaults to four parallel type-checking workers), --builders for parallel project-reference builds, and --singleThreaded to disable parallelization entirely, per Microsoft’s announcement. TypeScript 7.0 also locks in several configuration defaults introduced as options in TypeScript 6.0: strict: true, module: esnext, noUncheckedSideEffectImports: true, and a stableTypeOrdering setting that Microsoft says can no longer be disabled. The types compiler option now defaults to an empty array rather than including all @types packages by default. Several older options are removed outright, including target: es5, downlevelIteration, moduleResolution: node and node10, and the amd, umd, systemjs, and none module modes, according to Microsoft.
On why the team chose Go for the rewrite, The Register reports that Anders Hejlsberg — who, along with Steve Lucco, initially built TypeScript — explained in a Microsoft video: “It’s the lowest level language we can get to that gives us full native-code support on all platforms.” The outlet also quotes an earlier Hejlsberg remark on the performance split: “We quickly realized we could get 10x, half of it from being native code, and the other half from being able to take advantage of shared memory concurrency.”
What We Don’t Know
Microsoft’s announcement states: “Workflows that use Vue, MDX, Astro, Svelte, and others will likely not yet be able to leverage TypeScript 7. Similarly, specialized type-checking within templates like Angular will also likely not use TypeScript 7.” Support is pending an API expected in a future 7.1 release. Microsoft has not published a specific date for 7.1 or for when framework-embedded language support will land.
Analysis
The GA release closes out a migration path The Machine Herald has tracked since TypeScript 6.0 shipped as the final JavaScript-based release, through the 7.0 Beta in May and the RC in June. The compatibility package strategy — shipping tsc6 alongside the new native tsc binary — suggests Microsoft is betting that most projects can adopt the faster compiler immediately, while giving teams relying on unsupported framework tooling, such as Vue or Astro projects, an explicit off-ramp until the language-service API matures in a later release.