TypeScript 7.1 Beta in a Real Project: Run It Side by Side, Measure the Speedup and Fix What Breaks

1. The Problem: 7.0 Was Fast, but Half the Toolchain Couldn’t Follow

TypeScript 7.0 shipped on 8 July 2026 as the native Go port of the compiler. Microsoft reported typical speedups of 8–12× on full builds; the VS Code codebase went from 125.7 s to 10.6 s with the default four type-checker threads. The catch was spelled out in the announcement: 7.0 shipped without an API. Anything that imports the compiler as a library — typescript-eslint’s type-aware rules, Volar for Vue, svelte-check, Angular’s template checking — had to stay on 6.0.

So the question for a Next.js or Node team isn’t whether 7.x is fast — it is. It’s whether your whole toolchain can run on the same compiler, and what 7.1 changes in code that compiled cleanly on 7.0.

2. Minimal Concepts: What 7.1 Actually Changes

Six things, in the order they will reach you. The first two are why this release exists; the last one is why your build might fail.

3. Tutorial: 7.1 Beta in a Next.js Project Without Breaking Anything

Everything below ran in my sandbox on Windows 11 with Node 22.22 and npm 11.11, against typescript 7.1.0-beta, 7.0.2 and @typescript/typescript6 6.0.2 (whose tsc6 reports 6.0.3). I only tested npm; the outputs in the comments are the ones I got.

node -v
npx tsc -v                  # the compiler your scripts really run
npm ls typescript           # who else pulls in a TypeScript
npx tsc --noEmit --pretty false > typecheck-before.txt

# Path A: already green on 7.0, no typescript-eslint type-aware rules
npm install -D --save-exact typescript@7.1.0-beta

# Path B: "typescript" stays 6.0 for tools, tsc comes from 7.1
npm install -D --save-exact "typescript@npm:@typescript/typescript6@6.0.2" "@typescript/native@npm:typescript@7.1.0-beta"

npx tsc -v     # Version 7.1.0-beta
npx tsc6 -v    # Version 6.0.3   (Path B only)

// package.json after Path B
"devDependencies": {
  "@typescript/native": "npm:typescript@7.1.0-beta",
  "typescript": "npm:@typescript/typescript6@6.0.2"
}

// package.json
"scripts": {
  "typecheck": "tsc --noEmit",
  "typecheck:6": "tsc6 --noEmit",
  "bench:tsc": "node scripts/bench-tsc.mjs 5 tsconfig.json"
}

# .github/workflows/ci.yml — an extra job next to your normal build
  typecheck-ts71-beta:
    runs-on: ubuntu-latest
    continue-on-error: true          # informative until 7.1 is stable
    steps:
      - uses: actions/checkout@v5
      - uses: actions/setup-node@v5
        with:
          node-version: 22
          cache: npm
      - run: npm ci
      - run: npx tsc -v
      - run: npx tsc --noEmit --checkers 2

// scripts/bench-tsc.mjs  ·  usage: node scripts/bench-tsc.mjs [runs] [tsconfig]
import { spawnSync } from "node:child_process";
import { existsSync } from "node:fs";

const RUNS = Number(process.argv[2] ?? 5);
const PROJECT = process.argv[3] ?? "tsconfig.json";
const CHECKERS = process.env.CHECKERS; // e.g. CHECKERS=2 to mimic a small CI runner

// Explicit paths: never trust whatever node_modules/.bin/tsc points at today.
const compilers = [
  { label: "6.0", bin: "node_modules/typescript/bin/tsc6" },
  { label: "7.0", bin: "node_modules/ts70/bin/tsc" },
  { label: "7.1-beta", bin: "node_modules/@typescript/native/bin/tsc" },
].filter((c) => existsSync(c.bin));

const median = (xs) => [...xs].sort((a, b) => a - b)[Math.floor(xs.length / 2)];

for (const { label, bin } of compilers) {
  const args = [bin, "-p", PROJECT, "--noEmit", "--incremental", "false", "--extendedDiagnostics"];
  if (CHECKERS && label !== "6.0") args.push("--checkers", CHECKERS);

  const version = spawnSync(process.execPath, [bin, "-v"], { encoding: "utf8" }).stdout.trim();
  const wall = [];
  const mem = [];
  let exit = 0;

  for (let i = 0; i <= RUNS; i++) {
    const t0 = performance.now();
    const r = spawnSync(process.execPath, args, { encoding: "utf8", maxBuffer: 256 * 1024 * 1024 });
    const ms = performance.now() - t0;
    exit = r.status;
    if (i === 0) continue; // warm-up run: fills the OS file cache, not counted
    wall.push(ms);
    const m = /Memory used:\s+(\d+)K/.exec(r.stdout);
    if (m) mem.push(Number(m[1]) / 1024);
  }

  console.log(
    label.padEnd(9),
    version.padEnd(20),
    "median " + (median(wall) / 1000).toFixed(2) + " s",
    "| memory " + (mem.length ? median(mem).toFixed(0) + " MiB" : "n/a"),
    "| exit " + exit,
  );
}

// Path A: the default path above points at node_modules/typescript/bin/tsc instead.

type Show<A extends number, B extends A> = `${B} extends ${A}`;

type Issue<A extends number, B extends A> =
    A extends B ? never : Show<A, B>;
// 7.1: error TS2344: Type 'B' does not satisfy the constraint 'A'.
//   'B' is only assignable to the non-distributed 'A', but 'A' has been distributed here.

// Fix A: re-check the relation inside the branch (unsound combinations become never)
type FixA<A extends number, B extends A> =
    A extends B ? never : B extends A ? Show<A, B> : never;

// Fix B: drop a constraint the helper never needed (keeps the 7.0 result)
type ShowLoose<A extends number, B extends number> = `${B} extends ${A}`;
type FixB<A extends number, B extends A> =
    A extends B ? never : ShowLoose<A, B>;

// Fix C: stop distributing, if you meant the whole union (the result changes)
type FixC<A extends number, B extends A> =
    [A] extends [B] ? never : Show<A, B>;

// FixA<0 | 1, 0> = never
// FixB<0 | 1, 0> = "0 extends 1"
// FixC<0 | 1, 0> = "0 extends 0" | "0 extends 1"

// What 7.1 printed for a legacy Next.js tsconfig in my sandbox
// error TS5108: Option 'moduleResolution=node10' has been removed. Please remove it from your configuration.
// error TS5102: Option 'baseUrl' has been removed. Please remove it from your configuration.
//   Use '"paths": {"*": ["./*"]}' instead.

// tsconfig.json
{
  "compilerOptions": {
-   "moduleResolution": "node",
+   "moduleResolution": "bundler",
-   "baseUrl": ".",
    "paths": { "@/*": ["./src/*"] },
+   "types": ["node", "jest"],       // only if you rely on these globals
    "plugins": [{ "name": "next" }]
  }
}

// check-snippet.mjs: type-check generated code in memory with the TypeScript 7.1 API
import { API } from "@typescript/native/sync";
import { createFileSystemWithLib } from "@typescript/native/fs";
import { ScriptTarget } from "@typescript/native/ast";
import { resolve } from "node:path";

export function typecheck(code) {
  const fileName = resolve("virtual/generated.ts"); // never written to disk
  const api = new API();
  const snapshot = api.createSnapshot({
    fileSystem: createFileSystemWithLib([[fileName, code]]),
    createPrograms: [
      { rootFiles: [fileName], compilerOptions: { strict: true, noEmit: true, target: ScriptTarget.ES2022 } },
    ],
  });
  const program = snapshot.operation.createdPrograms[0];
  try {
    return program.getSemanticDiagnostics().map((d) => "TS" + d.code + ": " + d.text);
  } finally {
    program.dispose(); // these objects live on the Go side: release them explicitly
    snapshot.dispose();
    api.close();
  }
}

console.log(typecheck('export const total = (xs: number[]): number => xs.reduce((a, b) => a + b, "0");'));
// [ "TS2322: Type 'string' is not assignable to type 'number'." ]
console.log(typecheck("export const ok = (xs: number[]): number => xs.length;"));
// []

4. Ecosystem Status (26 October 2026) and the Decision Table

I checked npm metadata and the tracking issues today. A peer range says what a package accepts, not that it works, but a range that excludes 7.x means npm will complain and the tool will usually refuse to start.

5. Common Mistakes (Most of Them I Hit in the Sandbox)

Roughly in order of how much time they cost.

Conclusion

TypeScript 7.1 is the release that turns 7.x into a complete toolchain instead of a fast tsc running next to a 6.0 one: the API and content mappers are what typescript-eslint, Vue, Svelte and Astro were waiting for. On top of that, Microsoft’s own numbers show another 1.2–1.9× over 7.0 with noticeably less memory.

It’s still a beta, and the ecosystem hasn’t crossed over yet. Install it side by side, pin it, run it in a CI job that can’t block you, measure on your own repo, and fix the distributive-type errors now, while reports can still shape the RC.

Sources

• Microsoft — Announcing TypeScript 7.1 Beta
• Microsoft — Announcing TypeScript 7.0
• TypeScript issue #63702 — lib.d.ts updates for TypeScript 7.1
• TypeScript PR #64237 — stricter checks on distributive type parameters
• typescript-go PR #4712 — content mappers
• Next.js 16.3 release post
• Next.js docs — useTypeScriptCli
• typescript-eslint issue #10940 — use TS 7 for type information
• Vue Language Tools PR #6170 — content mapper (v4 alpha)
• TypeScript issue #64565 — VS Code extension and workspace TypeScript 7.x
• Digital Applied — TypeScript 7.1 beta: what to test