Update dependency typescript to v7

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 7.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v7.0.2

Compare Source

v6.0.3: TypeScript 6.0.3

Compare Source

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

v6.0.2: TypeScript 6.0

Compare Source

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

---

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 is behind base branch, 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.

[LBBO]

@claude please fix this CI issue

[claude]

Claude finished @LBBO's task in 5m 13s —— View job

---

CI investigation: typescript 7.0.2 breaks the E2E job

• Gather context (PR diff, CI logs)
• Identify root cause of CI failure
• Assess whether an in-repo code fix exists
• Report findings

What's failing: the E2E tests step of the failing run. next dev (started as Playwright's webServer) throws:

Unhandled Rejection: Error: It looks like you're trying to use TypeScript but do not have the required package(s) installed.
Please install typescript by running:
	pnpm install --save-dev typescript

…and then times out waiting for the dev server.

Why this is surprising: typescript is installed correctly — pnpm install --frozen-lockfile succeeds, and in the very same job pnpm typecheck (tsc --noEmit) and pnpm test (vitest, 78 tests) both pass cleanly with typescript@7.0.2. Only Next.js's own internal "do I have TypeScript?" probe inside next dev fails to recognize the package.

Root cause: TypeScript 7 is Microsoft's rewritten native (Go-based) compiler, and it ships a fundamentally different package layout than 5.x/6.x. That's visible directly in this PR's pnpm-lock.yaml diff — typescript@7.0.2 now pulls in ~20 new per-platform optional dependencies (@typescript/typescript-linux-x64, @typescript/typescript-darwin-arm64, etc.), the same pattern used by native-binary packages like esbuild/swc. That restructuring (in particular how the package now exposes/resolves its internals) is what trips up Next 16.2.10's built-in TypeScript detection, even though the CLI (tsc) itself works fine.

This is an upstream compatibility gap between next@16.2.10's TypeScript integration and the newly-released typescript@7.0.2 package layout — not a bug in this repo's application code, config, or tsconfig. There isn't an in-repo source change that fixes Next's internal detection logic.

Note on verification: I wasn't able to run pnpm install/pnpm exec next dev locally in this sandbox (no network/package-manager access with the current --allowedTools), so I couldn't directly inspect the installed typescript package's package.json to pin down the exact resolution mechanism Next.js chokes on. The diagnosis above is based on the CI logs and lockfile diff, which are quite conclusive, but a maintainer with local pnpm install access could confirm by running next dev directly.

Recommendation: This major bump (5.9.3 → 7.0.2, skipping 6.x) is exactly the kind of change your Renovate config already flags for manual review — automerge is disabled here because it's a major version. I'd suggest holding off on merging until Next.js ships a release compatible with TypeScript 7's new package format, then bumping both together. I did not push a revert of the typescript version myself since that would undo the very change this PR exists to make — let me know if you'd instead like me to pin typescript back to 5.9.3 (or the latest 6.x) on this branch to get CI green while you wait on Next.js support.