The biggest change to TypeScript since it launched doesn’t add a single new type feature. TypeScript 7.0, released on July 8, 2026, is the compiler and language service rewritten in Go, and it is dramatically faster.

The numbers

Installing it looks the same as ever (npm install -D typescript) and the command is still tsc. What changes is how long you wait. Microsoft published full-build times for well-known open-source projects:

Codebase TypeScript 6 TypeScript 7 Speed-up
VS Code 125.7s 10.6s 11.9x
Sentry 139.8s 15.7s 8.9x
Bluesky 24.3s 2.8s 8.7x
Playwright 12.8s 1.47s 8.7x
tldraw 11.2s 1.46s 7.7x

With --checkers 8, which spreads type checking across more threads, Microsoft measured speed-ups of 10.6x to 16.7x. Memory use fell by 6% to 26%. In the editor, the time to see the first error after opening a file in VS Code dropped from about 17.5 seconds to under 1.3 seconds.

The catch: no API yet

TypeScript 7.0 ships without a programmatic API, and the release notes say so directly. A new API is planned for 7.1. In the meantime, anything that drives the compiler from code can’t use 7.0. InfoQ lists Volar (Vue’s tooling), Angular’s tooling, webpack loaders and typescript-eslint among those affected.

Microsoft’s answer is to run both. The @typescript/typescript6 package installs a tsc6 binary, so your linters and framework tooling keep using TypeScript 6 while builds and type checks use 7.

New defaults, hard errors

7.0 also finishes the clean-up that 6.0 started:

  • New defaults: strict: true, module: esnext, types: [] and rootDir: ./.
  • Removed options are now errors: including target: es5, baseUrl, the node10 and classic module resolution modes, and AMD, UMD and SystemJS output.

If your project compiled cleanly on 6.0 without deprecation warnings, the upgrade is usually painless. If it relied on any of the above, fix those on 6.0 first.

Why it matters

Type checking is often the slowest step in a JavaScript CI pipeline and the main source of editor lag in large monorepos. Cutting it by an order of magnitude changes what is practical, such as type-checking on every save or on every pull request without caching tricks.

For most teams the sensible path for now is a split setup: TypeScript 7 for tsc --noEmit in CI and for the editor, TypeScript 6 for tools that need the API, until 7.1 lands. Microsoft’s blog listed a 7.1 beta in October.

Sources

  1. Microsoft TypeScript blog: Announcing TypeScript 7.0 (Jul 8, 2026)
  2. InfoQ: TypeScript 7 released (Aug 3, 2026)

We link every claim to the reporting or official statement it comes from. Where a detail rests on one outlet’s reporting, we say so. Spotted an error? Reply to any newsletter and we’ll correct it.