chore(deps-dev): bump typescript from 6.0.3 to 7.0.2

[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

Commits

• 1e4744d Merge branch 'main' into ts7-release
• a5a219cmicrosoft/typescript-go#4558
• ecfe30d Update status localization
• 5de25b5 Hide executable name in TypeScript status
• d7ce74a Show bundled TypeScript version for packaged servers
• 29be66a Correct TS 7 release version to 7.0.2
• ed2bd1b Merge branch 'main' into ts7-release
• 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
• 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
• d4eaca5microsoft/typescript-go#4549
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

[pullfrog]

Important

typescript@7.0.2 falls outside the declared peer ranges of svelte-check and @sveltejs/kit, and the non---tsgo half of bun run check may not work with it. Please confirm the checks CI job is green before merging.

Reviewed changes

Reviewed the single Dependabot commit bumping typescript from 6.0.3 to 7.0.2.

• package.json — devDependencies.typescript pinned to 7.0.2.
• bun.lock - the workspace block matches package.json. The typescript entry is now the native-port package with 20 @typescript/typescript-* platform optional dependencies and a tsc-only bin (the tsserver bin is gone).

⚠️ typescript@7 is outside the peer ranges of its main consumers

bun.lock:688 shows svelte-check@4.7.6 declaring typescript: ^5.0.0 || ^6.0.0, and bun.lock:280 shows @sveltejs/kit@3.0.1 declaring typescript: ^6.0.0. Neither admits 7.x. The repo's check script runs svelte-check --tsconfig ./tsconfig.json (the JS-API path) and then svelte-check --tsgo. The first pass depends on the classic typescript JS API, which the 7.x native package may not expose. That would fail the svelte-check prek hook, which runs in the checks CI job. I could not confirm this here because node_modules still holds 6.0.3 and bun ci and bun run check can't be re-run in the sandbox. Validation therefore rests on CI.

Technical details

# TypeScript 7 vs. peer ranges and svelte-check

## Affected sites
- `bun.lock:688` — `svelte-check@4.7.6` peer `typescript: ^5.0.0 || ^6.0.0`
- `bun.lock:280` — `@sveltejs/kit@3.0.1` peer `typescript: ^6.0.0`
- `package.json:15` — `check` script runs `svelte-check` without `--tsgo` first, which needs the TS JS API
- `.pre-commit-config.yaml:86` — `svelte-check` hook runs `bun run check`

## Required outcome
- The `checks` CI job (prek `--all-files`) passes with `typescript@7.0.2`, or the bump is held until `svelte-check` and `@sveltejs/kit` declare TS 7 support.

## Suggested approach (optional)
- If the non-tsgo pass fails, either hold this bump (ignore the TS major in Dependabot) or drop the non-tsgo `svelte-check` invocation if the `--tsgo` pass gives enough coverage.

## Open questions for the human
- Is the `check-peers` hook from `edbfi/edbfi-ci` expected to flag out-of-range peers? If so it may fail here too.

Nitpicks

• The lock no longer records a tsserver bin. Nothing in the repo references it, so this is harmless.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using claude-sonnet-5-5 ｜ 𝕏}