TypeScript 7 is 10x faster. Can your project actually use it?

TypeScript 7.0 shipped on July 8, 2026 with a compiler rewritten in Go. Full builds run 8 to 12 times faster, Microsoft's release post reports. VS Code's own build fell from 125.7 seconds to 10.6 seconds.

Then teams tried to upgrade and their lint step died. Here is the split: if you only run tsc, upgrade today. If you run type-aware ESLint, or you type-check Vue, Svelte, Astro or Angular templates, wait for TypeScript 7.1.

Key takeaways

• TypeScript 7.0 delivers 8x to 12x faster full builds, per Microsoft's release post, with VS Code at 11.9x and Sentry at 8.9x.
• TypeScript 7.0 ships with no programmatic API, so typescript-eslint, ts-jest, ts-morph and template type-checkers cannot run on it.
• The new API is the priority for TypeScript 7.1, which Microsoft frames on a 3 to 4 month cadence from the July 2026 release.

What TypeScript 7 actually changed

TypeScript is Microsoft's typed superset of JavaScript, and its compiler was itself written in TypeScript until this release. Version 7.0 replaces that self-hosted compiler with a native port written in Go.

That port is why the numbers moved. Microsoft's release post lists VS Code at 125.7 seconds down to 10.6 seconds, an 11.9x gain, and Sentry at 139.8 seconds down to 15.7 seconds, an 8.9x gain. InfoQ's coverage of the release reported the same headline figure of roughly 10x.

The type system itself is unchanged. Declarations continue to mean exactly what they meant under TypeScript 6.0. What changed is the implementation that evaluates them, alongside the integration interface that surrounding tools depend upon.

Why your lint step broke

A programmatic API is the interface that lets another program drive the compiler, rather than shelling out to a command. Tools do not re-implement type checking. They ask the compiler for the type of a node and act on the answer.

TypeScript 7.0 does not expose one. Microsoft's release post is explicit that tools which embed TypeScript into their own compilers and language services, such as Volar, can currently rely only on TypeScript 6.0.

That single gap is the whole compatibility story. typescript-eslint still declares a supported range of >=4.8.4 <6.1.0, which excludes 7.0 outright. Install TypeScript 7 next to it and npm reports a peer dependency conflict instead of a working setup.

A support request filed on release day, typescript-eslint issue #12518, was closed as not planned. The report notes that typescript-eslint 8.63.0 caps TypeScript below 6.1.0, which causes install conflicts and crashes with TypeScript 7.0.2.

Who can upgrade today, and who cannot

Setup	TypeScript 7.0 today?	Why
Plain tsc build or typecheck	Yes	The command line is the supported surface
Type-aware ESLint rules	No	typescript-eslint caps below 6.1.0
Vue, Svelte, Astro or MDX templates	No	Volar-based checkers need the API
Angular templates	No	Template checking needs the API
ts-jest, ts-morph, custom AST tooling	No	These call the compiler directly
Editor experience in VS Code	Yes	Editors use the language server, not the API

The distinction underneath that table is the compilation interface itself. Anything that invokes the compiler as an executable is compatible today. Anything that embeds the compiler as a library dependency remains blocked until the replacement interface arrives.

The staged upgrade that works now

tsgo is the name of the Go compiler build, developed in the microsoft/typescript-go repository and now shipped as the tsc inside the typescript package. You do not have to choose one version for everything. Microsoft made side-by-side use a priority, so tools that still need the API can stay on TypeScript 6.0.

1. Install TypeScript 7 as the build and typecheck compiler. Run npm install -D typescript, then npx tsc --noEmit in continuous integration.
2. Keep TypeScript 6 installed for the tools that need it, pinned as a separate dependency for ESLint and template checking.
3. Point your fast feedback loop at TypeScript 7. That is where the 10x lands, and it is the loop developers wait on.
4. Leave lint and template checks on the TypeScript 6 path until 7.1 ships.

For example, a monorepo can run type checking in about a tenth of the time on pull requests while its lint job still uses the older compiler. The build gets faster this quarter. The lint job gets faster in the autumn.

What lands in TypeScript 7.1, and when

The new programmatic API is the stated priority for 7.1, along with feature work and further performance gains, Microsoft's release post says. The team frames releases on a 3 to 4 month cadence, which puts 7.1 in roughly the October to November 2026 window from a July 8, 2026 start.

Treat that as a plan, not a promise. The API is described as new and different, not as a drop-in replacement for the old one. Tool authors must port to it after it ships. So there is a lag between the 7.1 release and the day typescript-eslint supports it.

That lag is the real scheduling question for a team. Plan the full migration for a quarter after the API lands, not the week of.

Should you upgrade now or wait?

Upgrade the build now if your type-check job is a bottleneck and your lint rules are not type-aware. The gain is large, the risk is contained, and rolling back is a version change.

Wait if you ship a Vue, Svelte, Astro or Angular application whose templates are type-checked in continuous integration. No local configuration compensates for an unavailable integration interface, and a partially migrated repository generates more maintenance overhead than a slower build does.

Consider the money side too, since build minutes are billed. A job that falls from 125.7 seconds to 10.6 seconds runs roughly 90% cheaper on a per-minute runner, using the comparison figures published in the TypeScript 7.0 performance section. On a repository with hundreds of pull requests a month, that is a real line item, and it is the argument that gets the upgrade prioritised.

Frequently asked questions

Is TypeScript 7 stable?

Yes. TypeScript 7.0 reached general availability on July 8, 2026 and is the version installed by npm install -D typescript. The gap is not in the compiler. It is the missing API that other tools depend on.

Why does typescript-eslint not support TypeScript 7?

TypeScript 7.0 ships with no stable API, and typescript-eslint drives the compiler as a library, not as a command. Its published support range is >=4.8.4 <6.1.0, so installing TypeScript 7 alongside it produces a peer dependency conflict.

Can I run TypeScript 6 and TypeScript 7 in the same repository?

Yes, and Microsoft made that path a priority. Use TypeScript 7 for tsc builds and type checking, and keep TypeScript 6 pinned for ESLint, ts-jest, ts-morph and template type-checkers until the new API arrives.

When will TypeScript 7.1 be released?

Microsoft has not published a date. The team describes a 3 to 4 month release cadence, which points at roughly October or November 2026 given the July 8, 2026 release of 7.0. The new programmatic API is the stated priority for that version.

How much faster is TypeScript 7 in practice?

Microsoft reports 8x to 12x on full builds. Two published examples are VS Code, from 125.7 seconds to 10.6 seconds, and Sentry, from 139.8 seconds to 15.7 seconds. Incremental builds and editor speed gain less, because those paths were already cached.