feat(npm)!: Update dependency typescript (6.0.3 → 7.0.2)

[sticky-gecko]

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 has been generated by Mend Renovate CLI.

[onedr0p]

Not adoptable yet — the Svelte toolchain has no TypeScript 7 support.

Why CI is red: svelte-check crashes at load (TypeError: Cannot read properties of undefined (reading 'useCaseSensitiveFileNames') — it dereferences ts.sys). That's not an interop wrinkle: typescript@7.0.2 is the Go-native compiler and ships no JS compiler API at all. Its main entry exports only version/versionMajorMinor, with the new native API surfaced under typescript/unstable/* — no ts.sys, no language service, nothing the legacy API consumers can run on:

$ node -e 'const ts=require("typescript"); console.log(Object.keys(ts), "sys?", !!ts.sys)'
[ 'version', 'versionMajorMinor' ] sys? false

Why there's no version combo that fixes it: svelte-check is built on the legacy TS language service, and its latest release (4.7.2, published 2026-07-07 — what we're already on) is still legacy-API-based; there is no TS7-capable svelte-check. And in internal/web, svelte-check is the only consumer of the typescript package (no tsc in any script; Vite/esbuild handles transpilation) — so there's nothing else that could meaningfully move to 7 either.

Revisit condition: sveltejs/language-tools shipping a svelte-check built on the TS7 native API (typescript/unstable/* or the LSP). Until then this PR stays parked; Renovate will keep rebasing it, and it can merge the moment a compatible svelte-check exists.

[greptile-apps]

Greptile Summary

This PR upgrades the frontend TypeScript dependency and lockfile. The main changes are:

• typescript moves from ^6.0.3 to ^7.0.2 in internal/web/package.json.
• internal/web/package-lock.json is refreshed for typescript@7.0.2.
• The lockfile adds TypeScript's platform-specific optional packages.

Confidence Score: 4/5

This PR needs a tooling compatibility fix before merging.

A single contained issue affects the frontend typecheck workflow: typescript@7.0.2 is incompatible with the existing svelte-check@4.7.3 script.

Files Needing Attention: internal/web/package.json, internal/web/package-lock.json

T-Rex Logs

What T-Rex did

• The typecheck failure was reproduced under the internal frontend setup when using TypeScript 7.0.2 and svelte-check 4.7.3.
• The dependency state was checked and shows TypeScript 7.0.2 is installed and resolved.
• The typecheck crashed with a TypeError reading useCaseSensitiveFileNames before validating the Svelte app.
• A production build was performed and produced assets, including dist/index.html, with the build completing in 766ms and exit code 0.
• Artifacts were prepared to enable reviewers to inspect both the reproduction and the production build.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
internal/web/package.json	Updates the TypeScript devDependency to 7.0.2, which conflicts with the existing svelte-check typecheck workflow.
internal/web/package-lock.json	Refreshes the lockfile for TypeScript 7.0.2 and its platform-specific optional packages.

_{Reviews (5): Last reviewed commit: "feat(npm)!: Update dependency typescript..." | Re-trigger Greptile}

[greptile-apps]

Breaks Svelte typecheck
npm run typecheck still runs svelte-check, but svelte-check@4.7.3 embeds TypeScript's programmatic APIs and is not compatible with the TypeScript 7 package layout. The updated lockfile also shows typescript@7.0.2 only exposes the tsc bin, so the existing typecheck script will fail instead of validating the Svelte app.

Artifacts

Repro: npm run typecheck failure with TypeScript 7.0.2 and svelte-check 4.7.3

• The full command output behind this check.

_{Ran code and verified through T-Rex}

[sticky-gecko]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: internal/web/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: svelte-check@4.7.5
npm error Found: typescript@7.0.2
npm error node_modules/typescript
npm error   dev typescript@"^7.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@"^5.0.0 || ^6.0.0" from svelte-check@4.7.5
npm error node_modules/svelte-check
npm error   dev svelte-check@"^4.7.5" from the root project
npm error
npm error Conflicting peer dependency: typescript@6.0.3
npm error node_modules/typescript
npm error   peer typescript@"^5.0.0 || ^6.0.0" from svelte-check@4.7.5
npm error   node_modules/svelte-check
npm error     dev svelte-check@"^4.7.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2026-08-07T15_19_35_746Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-08-07T15_19_35_746Z-debug-0.log