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.

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[jaiew]

Why this fails

npm ci fails with an ERESOLVE conflict, not a flaky CI issue:

npm error peer typescript@">=4.8.4 <6.1.0" from typescript-eslint@8.65.0
npm error Conflicting peer dependency: typescript@6.0.3

typescript-eslint (all 8.x releases, including the current latest 8.69.0, published 2026-08-31 — a month after typescript@7.0.2 shipped) still caps its typescript peer dependency at <6.1.0. This isn't a stale/unmaintained peer-dep range — it's deliberate: TypeScript 7.0 shipped with a new Go-ported compiler ("tsgo"), and the compiler API @typescript-eslint/typescript-estree depends on internally isn't available yet on that new compiler. Forcing past the peer-dep check (--legacy-peer-deps/--force) doesn't actually work either — upstream reports linting crashes at runtime (TypeError: Cannot read properties of undefined (reading 'Cjs') in typescript-estree's create-program/shared.js) when TS 7 is force-installed.

This is tracked upstream:

• typescript-eslint#10940 — open, labeled blocked by external API: typescript-eslint is waiting on TypeScript itself to expose a stable compiler API for the new Go compiler.
• typescript-eslint#12518 — closed as duplicate/not-planned, maintainer confirmed: "typescript-eslint isn't compatible with TS 7 at this time, because there is no TS 7 API at this time."

That stable API is expected to land in TypeScript 7.1, not yet released as of 2026-09-04.

Is there a workaround?

TypeScript's own migration guide describes running TS 6 and TS 7 side-by-side (aliasing an old typescript install specifically for tooling that needs it, while using 7.x for the actual build) — see the TypeScript 7.0 announcement. For this repo that would mean npm-aliasing a second typescript@6.x install just for typescript-eslint while keeping typescript@7.x for tsup's build. That's meaningful added complexity (alias package, dual-version maintenance) for a library that doesn't have a pressing reason to move to TS 7 today.

Recommendation

Don't merge this yet — holding until typescript-eslint ships official TS 7 support (or TS 7.1's stable API lands and typescript-eslint adopts it). No action needed here beyond letting Dependabot keep this PR up to date; re-evaluate once typescript-eslint's peer dependency range includes 7.x.