What TypeScript 7.1 Beta means for your toolchain

Microsoft has released TypeScript 7.1 Beta, the first update to the Go-based compiler that shipped as TypeScript 7.0 in July, according to InfoQ. The change that decides what this means for you is that 7.1 restores the compiler API that 7.0 dropped. InfoQ reports that without that API, tools that embed the compiler, from Vue’s Volar to Svelte, Astro, ts-morph and type-aware linting, were “stranded on TypeScript 6” for three months.

The background you need

TypeScript is two things. It is a language: JavaScript plus optional type annotations. It is also a program, the compiler, usually run as tsc. The compiler reads your code, checks that the types line up, and turns it into plain JavaScript. Your editor runs a language server in the background. That is a long-running process built on the same compiler, and it powers red squiggles, autocomplete and go-to-definition.

A compiler API is a way for other programs to use the compiler as a library instead of running it as a command. Many tools you rely on do this without telling you:

• Framework language tools. Vue’s Volar is an example. It lets your editor understand .vue files.
• Code transformation libraries such as ts-morph, which read and rewrite TypeScript source.
• Type-aware lint rules. These are lint checks that ask the compiler what type a value has before deciding whether to warn you.

Since version 7.0, the TypeScript compiler has been written in Go instead of in TypeScript itself, according to InfoQ. That native port is where the speed gains come from. The catch is that the old API was a JavaScript module that tools loaded straight into their own process. A compiled Go program cannot simply be imported into Node.js like a JavaScript library. The API had to be rebuilt as something that talks to the compiler from the outside, and 7.0 shipped without it.

An analogy helps here. Think of the compiler as a car engine and the API as the diagnostic port that mechanics plug their tools into. Version 7.0 swapped in a much faster engine but left out the port. Drivers who never open the hood could move to the new car. Mechanics, meaning framework and tool authors, had to keep working on the old model, TypeScript 6. The analogy breaks in one place. The new port is not one socket but several smaller ones, and some plugins now run as separate processes rather than inside the engine.

One more term: non-standard files. A Vue or Svelte component lives in a single file that mixes a template, a script and styles. TypeScript does not understand that format. Framework tools translate each component into a virtual TypeScript file, check it, and then map any error back to the right line in your original component. Until now, Vue did this through a separate wrapper binary called vue-tsc.

What actually changed in 7.1

The Go compiler and its speed are not new. Those arrived with 7.0. What is new in the beta, according to InfoQ:

The compiler API is back, in a new shape. Instead of reviving one large module, 7.1 splits it into focused entry points such as typescript/sync, typescript/async, typescript/fs and typescript/ast. Those paths previously sat behind an unstable prefix, which has now been dropped. The client also models editor changes through reusable snapshots, so a tool can build new state from old state without starting over. The team says the API surface will stay backward compatible across all of 7.x once it is stable.

Content mappers. InfoQ calls this the beta’s most discussed feature. It is a supported plugin point that lets a package hand TypeScript a virtual view of a file such as .vue or .svelte, with mappings back to the original. A mapper runs as a separate process and only when you opt in. The team warns that the flag should be treated like any build plugin, meaning you are choosing to run someone else’s code in your build.

Vue is already porting. Maintainer Johnson Chu has shipped a Vue Language Tools v4 alpha on top of content mappers. It drops vue-tsc in favour of a @vue/content-mapper that runs inside tsc itself. In a migration write-up cited by InfoQ, the Directus admin app (581 Vue components across 882 TypeScript files) saw type checks fall from 14.19 to 3.10 seconds. That is a 4.6x speedup over vue-tsc 3.

Speed and memory. Microsoft’s MUI docs benchmark falls from 22.2 to 11.9 seconds while roughly halving memory. Heavier codebases such as VS Code see closer to 1.2x. An independent NestJS test put a 353,000-line check at 2.76 seconds on the beta, against 4.95 on 7.0 and 12.42 on the old compiler. The same test flagged a memory regression in 7.0 that 7.1 reverses.

Language additions. Import attributes in ambient module declarations, TC39 source phase imports for loading WebAssembly, and a stable es2026 target that includes Math.sumPrecise() and Error.isError().

Daniel Rosenwasser announced the beta on 20 October 2026. InfoQ reports that the iteration plan tentatively places a release candidate and stable build in late November, and that the beta arrived two weeks behind schedule.

What it means if you deploy and run apps

The restored API matters more than the benchmarks. A faster compiler does nothing for you if a tool in your chain cannot talk to it. Your real question is not how fast 7.1 is. It is whether anything you depend on embeds the compiler.

InfoQ’s guidance breaks down like this:

• Still on TypeScript 5? Move through 6 to 7 rather than jumping straight to 7.
• Using Vue, Svelte or Angular? Keep a dual TypeScript 6 and 7 install until your framework tooling ships a 7.1 build.
• Trying the Vue beta tooling? The Directus write-up’s author flagged that you would need to run 7.1 in CI alongside an older TypeScript in the editor until Vue tooling stabilises on the stable release.
• Maintaining a tool or library? Port to the new entry points now and report missing functions through the API status tracker while gaps can still be filled before stable.

If you rely on ts-morph or type-aware lint rules, InfoQ lists them among the stranded tools but gives no separate upgrade advice. Check those projects’ own release notes for 7.1 support before you move.

What to watch next: whether the stable build lands in late November, when your framework’s tooling publishes a 7.1-compatible release, and the open GitHub issue described below.

What we don’t know yet

• The stable date. Late November is a tentative target, and the beta itself slipped two weeks.
• Svelte, Astro and Angular timing. InfoQ describes Vue’s alpha in detail but gives no dates for other frameworks shipping 7.1 builds. Angular appears in the dual-install advice but not in the list of tools that were stranded, and the report does not explain its situation further.
• API gaps. The team is asking authors to flag missing functions, which means the new API does not yet cover everything tools need.
• A known editor bug. On GitHub, Akira Higuchi reported that in a particular editor workflow, saving a mapper’s watched configuration file could leave types stale until the language server is restarted. InfoQ says the issue remains open.
• Your own speedup. The reported gains range from about 1.2x for VS Code to roughly 2x for MUI. Where your codebase lands is something only your own measurement will tell you.