[deps]: Update 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
  • "every 2nd week starting on the 2 week of the year before 4am 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.

[github-actions]

🤖 Bitwarden Claude Code Review

Overall Assessment: REQUEST CHANGES

Renovate bumps typescript from 6.0.3 to 7.0.2 across package.json and package-lock.json; no source files change. The lock file confirms this is the native Go compiler rewrite rather than a routine major — tsserver is removed from bin and 20 @typescript/typescript-<os>-<arch> platform binaries are added as optionalDependencies of the existing typescript package. Manifest and lock file are consistent, and the added packages are transitive optional dependencies of an already-approved dependency, so no new-dependency approval is required. Both Build and test jobs are currently failing on this PR, and this review could not read the job logs to attribute the cause.

Code Review Details

• ❓ : TypeScript v6 → v7 is the native compiler rewrite; ts-node@10.9.2 consumes the JS compiler API and drives four CI steps plus pretest's tsc emit — worth verifying before merge
  • package.json:29

Dependency Changes

Package	Change	Ecosystem
typescript	6.0.3 → 7.0.2 (major)	npm

[claude]

❓ QUESTION: TypeScript v6 → v7 is the native compiler rewrite — was ts-node compatibility verified?

Why this bump differs from a normal major

The lock file shows this is not an incremental major: tsserver is dropped from bin, and 20 @typescript/typescript-<os>-<arch> native binaries are added as optionalDependencies. TypeScript 7 is the Go port, and the JS compiler API surface that v6 exposed is the reason the 6.x line exists in parallel.

ts-node@10.9.2 loads that JS compiler API from the typescript peer dependency at runtime. It drives seven entry points here, four of which run in CI (test-all.yml):

• npm run setup:flags → scripts/match-server-config.ts
• npm run setup:crypto → scripts/generate-crypto.ts
• npm run seed:vault:account → scripts/create-account.ts
• npm run seed:vault:ciphers → scripts/seeder.sh:70 → scripts/vault-seeder.ts

Plus setup:install, setup:flags:ci, and benchmark locally. pretest also runs tsc --incremental -p tests/tsconfig.json, which must still emit into tests-out/ for every spec to run.

Both Build and test jobs are currently red on this PR. If the failure is unrelated (e.g. the bitwarden/clients artifact download), it would be worth confirming a local npm run pretest && npm run setup:crypto succeeds against 7.0.2 before merging; if ts-node cannot consume the native package, pinning typescript to the 6.x line until ts-node is replaced (e.g. with tsx) is the smaller change.