deps(deps-dev): bump typescript from 5.9.3 to 7.0.2

[dependabot]

Bumps typescript from 5.9.3 to 7.0.2.

Release notes

Sourced from typescript's releases.

TypeScript 6.0.3

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

TypeScript 6.0

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

TypeScript 6.0.1 RC

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).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

Commits

• See full diff in compare view

Maintainer changes

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

[scttfrdmn]

Investigated this locally (checked out the PR branch, ran npm ci, npm run typecheck, npm run build:lib). Not safe to merge yet — two independent blockers:

1. Peer dependency conflict (this is why CI is red):

typedoc@0.28.20 declares peerDependencies.typescript: "5.0.x || ... || 5.9.x || 6.0.x" — it doesn't accept 7.x at all. npm ci fails with ERESOLVE:

npm error While resolving: typedoc@0.28.20
npm error Found: typescript@7.0.2
npm error Could not resolve dependency:
npm error peer typescript@"5.0.x || ... || 5.9.x || 6.0.x" from typedoc@0.28.20

typedoc's next/dev channel (1.0.0-dev.4) relaxes this to typescript: ">=4.0.0", but that's a pre-release, not something we should pull in just to unblock this bump.

2. Real type errors underneath, once you force past the peer conflict (npm ci --legacy-peer-deps):

src/ssm/session.ts(156,19): error TS2345: Argument of type 'Uint8Array<ArrayBufferLike>' is not assignable to parameter of type 'string | Blob | BufferSource'.
  Type 'Uint8Array<ArrayBufferLike>' is not assignable to type 'ArrayBufferView<ArrayBuffer>'.
    ...
        Type 'SharedArrayBuffer' is not assignable to type 'ArrayBuffer'.
src/ssm/session.ts(174,19): error TS2345: [same error, second call site]
src/terminal.ts(7,8): error TS2882: Cannot find module or type declarations for side-effect import of '@xterm/xterm/css/xterm.css'.

The session.ts errors are from TS7's stricter ArrayBufferLike/SharedArrayBuffer typing on WebSocket.send() — a real typing change, not a config issue, and would need actual code changes (e.g. narrowing/copying the buffer) in src/ssm/session.ts:156 and :174. The terminal.ts one (TS2882) is a new diagnostic for side-effect CSS imports without ambient type declarations.

Recommendation: hold this one. TypeScript 6.x isn't out as a Dependabot PR yet (dependabot skipped straight to 7.0.2), and typedoc doesn't support 6.x or 7.x yet either. Worth revisiting once typedoc ships a release with 7.x in its peerDependencies range, and someone budgets time to fix the two session.ts call sites and the terminal.ts CSS import typing. Leaving this open rather than merging.