chore(deps-dev): Bump typescript from 6.0.3 to 7.0.2

[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[JohnRDOrazio]

Hold this one — it's blocked by typescript-eslint, not by Next.js. The green checks are misleading; details below.

Next.js is fine

TypeScript 7 support (vercel/next.js#95639) merged to canary on 2026-07-10 and is in our next@16.3.0 (published 2026-08-03) — compare/v16.3.0...a249dcbcee72 reports ahead_by=0, behind_by=346, i.e. the commit is an ancestor of the tag.

We also don't need the experimental.useTypeScriptCli opt-in: next detects TS 7 and shells out to the CLI on its own. Verified by planting a deliberate type error and building on this branch:

Running TypeScript ...
lib/__ts7probe.ts(3,14): error TS2322: Type 'string' is not assignable to type 'number'.
Failed to type check.      (exit 1)

That check mattered because TS 7 no longer ships the JS Compiler API at all — its lib/ contains only getExePath.js, tsc.js, version.cjs, no typescript.js — so next's default API backend couldn't have worked. It correctly falls back rather than silently skipping.

On a clean tree with this bump: npx tsc --noEmit exits 0, npm run build succeeds, npm test passes 155 tests.

What actually breaks

npm run lint cannot start:

typescript-eslint does not support TS 7.0.
Please see https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/#running-side-by-side-with-typescript-6.0
to run typescript-eslint using the TS 6 API.
See also https://github.com/typescript-eslint/typescript-eslint/issues/10940
for tracking typescript-eslint's support for TS >=7.1

Two things make this awkward to work around:

1. Not fixable from our manifest. The failing typescript-eslint@8.67.0 is nested under eslint-config-next (node_modules/eslint-config-next/node_modules/typescript-eslint), not a direct dependency.
2. 7.0 specifically is unsupported. The upstream tracking issue is scoped to TS >= 7.1, so the likely path forward is TypeScript 7.1 plus a typescript-eslint release, not a fix for 7.0.

Why CI didn't catch it

No workflow ran eslint — the lint check in this PR is lint-markdown.yml, which only covers markdown. #288 adds an eslint job to close that gap. Once it lands, this PR's checks will fail honestly, though it will need a rebase or a push to re-run.

Suggested disposition

Leave open (or close and let dependabot re-raise) until typescript-eslint supports TS 7.x. Nothing here is a Next.js problem, and the TypeScript side of the bump is clean — it's purely the lint toolchain.