Update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	6.0.3 → 7.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 26a5e3a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[claude]

Claude finished @renovate[bot]'s task in 1m 35s —— View job

---

Review: Update dependency typescript to v7

Todo list

• Gather context (diff, repo structure, CLAUDE.md — none exists)
• Check TypeScript v7 compatibility implications (major version bump)
• Check CI status / attempt build+test locally
• Review package.json / lockfile diff for correctness
• Post final review feedback

Summary

This is a renovate-generated, mechanical dependency bump (typescript 6.0.3 → 7.0.2) touching only package.json and pnpm-lock.yaml — no source code changes to review for logic/security/performance.

However, CI is currently red, and it's a real, actionable problem rather than flakiness:

• The build (24.x) job's pnpm lint step fails (job log):

  TypeError: Cannot read properties of undefined (reading 'Cjs')
      at .../@typescript-eslint/typescript-estree@8.63.0_typescript@7.0.2/.../create-program/shared.js:59:18
  

  @typescript-eslint/typescript-estree@8.63.0 touches a TS compiler-internal enum that changed shape in TypeScript 7's rewrite, and the current typescript-eslint@8.x line doesn't yet declare support for TS 7. Left as-is, eslint --max-warnings=0 . (and therefore pnpm lint) crashes on every future PR until this is resolved — I've left an inline comment on package.json:64 with details and a "Fix this" link.
• By contrast, pnpm test (tsc --noEmit && tsdown && node run-tests.js) passes: type-checking, the tsdown build, attw, publint, and all 20 tests succeed under TypeScript 7. So the package's own source is compatible.
• Worth noting: the tsdown build log emits TypeScript 7.0 does not yet have a stable API and is experimental. Some options will be unavailable. — this is TypeScript upstream's own caveat about 7.0's compiler API, meaning tooling that reaches into TS internals (like typescript-eslint) may keep needing patches across 7.0.x point releases.

Recommendation

Don't merge yet. Hold this PR until typescript-eslint publishes a release with confirmed TypeScript 7 support (renovate may pick that up automatically as a separate PR), then re-run CI. Merging now would leave main's lint step permanently broken.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (27e9e1c) to head (26a5e3a).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #509   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines          273       273           
  Branches         6         6           
=========================================
  Hits           273       273           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[claude]

This update breaks CI right now. The build (24.x) job's pnpm lint step fails because @typescript-eslint/typescript-estree@8.63.0 is not compatible with typescript@7.0.2:

TypeError: Cannot read properties of undefined (reading 'Cjs')
    at .../@typescript-eslint/typescript-estree/dist/create-program/shared.js:59:18

(See job run.) typescript-estree reaches into a TS compiler-internal enum (module-kind related) that no longer exists in the same shape after TypeScript 7's rewrite. typescript-eslint's published peer range for the 8.x line does not extend to TS 7 yet, so eslint --max-warnings=0 . crashes outright rather than just warning.

Separately, tsdown's build log for this PR prints: TypeScript 7.0 does not yet have a stable API and is experimental. Some options will be unavailable. — tsc --noEmit, the tsdown build, and the test suite all pass, so this project's own source is fine under TS 7, but the toolchain (typescript-eslint) is the blocker, and the "experimental/unstable API" warning means downstream tools relying on TS's internal APIs could keep breaking across 7.0.x patch releases.

Recommend holding this PR until typescript-eslint ships a release with confirmed TypeScript 7 support (or renovate group-bumps it alongside), rather than merging with a red lint job.

Fix this →

[claude]

Claude finished @renovate[bot]'s task in 1m 10s —— View job

---

Review: Update dependency typescript to v7

Todo list

• Check what changed since the last review (new commit / rebase)
• Re-check CI status
• Re-verify lint/build/test locally if needed
• Post updated feedback

Summary

Re-checked this PR after it was re-triggered. Nothing has changed — the diff (package.json +1/-1, pnpm-lock.yaml +271/-70) and the single commit are identical to the last review, and the same commit is still typescript 6.0.3 → 7.0.2.

CI is still red for the same reason as before:

• build (24.x) → pnpm lint still fails (latest run):

  TypeError: Cannot read properties of undefined (reading 'Cjs')
      at .../@typescript-eslint+typescript-estree@8.63.0_typescript@7.0.2/.../create-program/shared.js:59:18
  

  @typescript-eslint/typescript-estree@8.63.0 (pinned in package.json:65) is still incompatible with typescript@7.0.2 — it reaches into a TS compiler-internal enum whose shape changed in TS 7's rewrite, and typescript-eslint@8.x's peer range doesn't yet declare TS 7 support.
• pnpm test (tsc --noEmit && tsdown && node run-tests.js) still passes — type-checking, the tsdown build, attw, publint, and all 20 tests succeed under TypeScript 7, so the project's own source remains compatible.

My inline comment on package.json:64 from the previous review still applies and is unchanged.

Recommendation

Still don't merge. Hold until typescript-eslint publishes a release with confirmed TypeScript 7 support and pnpm lint passes in CI. No code changes were made by this review since none were requested and the diff itself is fine — the blocker is purely the toolchain incompatibility.

[claude]

Claude finished @renovate[bot]'s task in 1m 3s —— View job

---

Review: Update dependency typescript to v7

Todo list

• Check what changed since the last review (re-triggered run)
• Re-check CI status
• Re-verify lint failure details
• Post updated feedback

Summary

Re-checked after this PR was re-triggered again. Nothing has changed since the previous two reviews — the diff (package.json +1/-1, pnpm-lock.yaml +271/-70), the single commit, and the dependency versions (typescript@7.0.2, typescript-eslint@8.63.0) are all identical.

CI is still red for the exact same reason:

• build (22.x) and build (24.x) → pnpm lint still fail (latest 24.x run):

  TypeError: Cannot read properties of undefined (reading 'Cjs')
      at .../@typescript-eslint+typescript-estree@8.63.0_typescript@7.0.2/.../create-program/shared.js:59:18
  

  @typescript-eslint/typescript-estree@8.63.0 (package.json:65) still reaches into a TS compiler-internal enum whose shape changed in TypeScript 7's rewrite, and the typescript-eslint@8.x line's peer range does not declare TS 7 support.
• coverage job (which runs pnpm test → tsc --noEmit && tsdown && node run-tests.js) still passes — type-checking, the build, and all tests remain compatible with TypeScript 7.

I don't have network access in this sandbox to check whether a newer typescript-eslint release with TS 7 support has since been published — worth checking npm view typescript-eslint versions manually before the next retry.

Recommendation

Still don't merge as-is. Hold until typescript-eslint ships confirmed TypeScript 7 support and pnpm lint passes, or explicitly downgrade/pin typescript-eslint's TS peer handling in this PR. No new code changes were made — the diff itself is fine, the blocker remains the toolchain incompatibility, unchanged since the last two reviews.

[claude]

Claude finished @renovate[bot]'s task in 54s —— View job

---

Review: Update dependency typescript to v7

Todo list

• Check what changed since the last review (re-triggered run)
• Re-check CI status
• Re-verify lint failure details
• Post updated feedback

Summary

Re-checked after this PR was re-triggered again. Nothing has changed since the previous three reviews — the diff (package.json +1/-1, pnpm-lock.yaml +271/-70), the single commit, and the pinned versions (typescript@7.0.2, typescript-eslint@8.63.0 at package.json:64-65) are all identical.

CI is still red for the exact same reason:

• build (22.x) → pnpm lint still fails (latest run), with build (24.x)/build (26.x) cancelled as a result:

  TypeError: Cannot read properties of undefined (reading 'Cjs')
      at .../@typescript-eslint+typescript-estree@8.63.0_typescript@7.0.2/.../create-program/shared.js:59:18
  

  @typescript-eslint/typescript-estree@8.63.0 (package.json:65) still reaches into a TS compiler-internal enum whose shape changed in TypeScript 7's rewrite, and the typescript-eslint@8.x line's peer range does not declare TS 7 support.
• The coverage job (pnpm test → tsc --noEmit && tsdown && node run-tests.js) still passes — type-checking, the build, and all tests remain compatible with TypeScript 7. The project's own source is fine under TS 7.

I still don't have network access in this sandbox to check whether a newer typescript-eslint release with TS 7 support has been published since the last check — worth verifying npm view typescript-eslint versions manually before the next retry.

Recommendation

Still don't merge as-is. Hold until typescript-eslint ships confirmed TypeScript 7 support and pnpm lint passes, or explicitly resolve typescript-eslint's TS peer handling in this PR. No new code changes were made — the diff itself is fine, the blocker remains the same toolchain incompatibility flagged in all prior reviews.

[claude]

Claude finished @renovate[bot]'s task in 1m 1s —— View job

---

Review: Update dependency typescript to v7

Todo list

• Check what changed since the last review (re-triggered run)
• Re-check CI status
• Re-verify lint failure details / check if typescript-eslint has been bumped
• Post updated feedback

Summary

Re-checked after this PR was re-triggered again. Nothing has changed since the previous four reviews — the diff (package.json +1/-1, pnpm-lock.yaml +271/-70), the single commit, and the pinned versions (typescript@7.0.2, typescript-eslint@8.63.0 at package.json:64-65) are all identical.

CI is still red for the exact same reason:

• build (22.x) → pnpm lint still fails (latest run), with build (24.x)/build (26.x) cancelled as a result:

  TypeError: Cannot read properties of undefined (reading 'Cjs')
      at .../@typescript-eslint+typescript-estree@8.63.0_typescript@7.0.2/.../create-program/shared.js:59:18
  

  @typescript-eslint/typescript-estree@8.63.0 (package.json:65) still reaches into a TS compiler-internal enum whose shape changed in TypeScript 7's rewrite, and the typescript-eslint@8.x line's peer range does not declare TS 7 support.
• The coverage job (pnpm test → tsc --noEmit && tsdown && node run-tests.js) still passes — type-checking, the build, and all tests remain compatible with TypeScript 7. The project's own source is fine under TS 7.

I still don't have network access in this sandbox to check whether a newer typescript-eslint release with TS 7 support has been published since the last check — worth verifying npm view typescript-eslint versions manually before the next retry.

Recommendation

Still don't merge as-is. Hold until typescript-eslint ships confirmed TypeScript 7 support and pnpm lint passes, or explicitly resolve typescript-eslint's TS peer handling in this PR. No new code changes were made — the diff itself is fine, the blocker remains the same toolchain incompatibility flagged in all prior reviews (5 consecutive re-checks now, all identical).