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.

[jmwerk]

Holding this one back — CI fails on npm ci with a real peer-dependency conflict, not a flake:

npm error ERESOLVE could not resolve
npm error While resolving: ts-jest@29.4.12
npm error Found: typescript@7.0.2
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <7" from ts-jest@29.4.12

ts-jest@29.4.12 (the currently installed version) declares a peer range of typescript@">=4.3 <7", so it doesn't yet support TypeScript 7.x. Bumping typescript alone breaks install; this would need a compatible ts-jest release (or a switch to --legacy-peer-deps, which isn't a real fix) before it can land.

Merged the other three Dependabot PRs (#77 joi, #76 eslint, #74 @types/vscode) since their CI was green. Leaving this one open until ts-jest ships TS7 support.

[jmwerk]

Dug in further to see whether this is fixable now — it isn't, from either side.

I checked out this branch and ran the full suite with npm ci --legacy-peer-deps to bypass the resolver conflict. tsc --noEmit passes cleanly (TypeScript 7's public compiler API is compatible), but npm test fails 52/53 suites with:

The TypeScript compiler "typescript" (version 7.0.2) does not expose the JavaScript compiler API
required by ts-jest. To use TypeScript 7 for project type-checking, install it as "@typescript/native"
and alias "@typescript/typescript6" as "typescript" for ts-jest.

This isn't a peer-range formality — TypeScript 7 ships a native Go-compiled tsc, and the JS-hosted compiler API ts-jest depends on for transforms is gone from the typescript package. ts-jest's own error names the intended migration path, but I checked and @typescript/native returns a 404 on the npm registry — it hasn't been published yet, so even the documented workaround isn't usable today.

Net: there's no way to make this PR's test suite pass right now, regardless of ts-jest version. This is blocked on the @typescript/native / typescript6-alias packages actually shipping upstream. Recommend leaving this PR open and revisiting once that lands (or once ts-jest publishes a release built against it) — I don't think ·@·d·ependabot i·gnore t·his major version is right either, since this should be picked back up as soon as the ecosystem catches up.

[jmwerk]

Can't merge this as-is: CI fails with an ERESOLVE conflict because ts-jest@29.4.12 (the latest published version — nothing newer or even pre-release exists yet) still pins its typescript peer dependency at >=4.3 <7. There's no ts-jest release yet that supports TypeScript 7's new architecture, so there's nothing to bump it to alongside this.

This is blocked upstream, not something fixable in this repo right now. Leaving it open — worth revisiting once ts-jest ships TS7 support.