chore(deps): update devdependency 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
  • "on Monday"
• 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nuxt-mcp-toolkit-docs	Error		Jul 30, 2026 7:22pm

[HugoRCD]

Investigated this one — it can't be merged yet.

TypeScript 7 ships a completely rewritten package layout: the default entry point ("main": "./lib/version.cjs") no longer exposes the classic Compiler API (convertCompilerOptionsFromJson, etc.). That API only exists under new typescript/unstable/* subpaths with a different shape.

@nuxt/module-builder (used by dev:prepare/build:module) still does import { convertCompilerOptionsFromJson } from 'typescript', which now fails at runtime (Named export 'convertCompilerOptionsFromJson' not found). This breaks dev:prepare for every workspace, so build, lint, typecheck, and test all fail in CI — even the latest @nuxt/module-builder@1.0.3 still has this issue.

This isn't something we can safely patch around in this repo (it would mean patching a third-party package that transitively affects most of the JS build tooling ecosystem, not just us). We should wait until @nuxt/module-builder (and likely mkdist/unbuild) ship TS7 support, then retry.

Leaving this PR open for Renovate to keep tracking; not merging for now.