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

[dependabot]

Bumps typescript from 6.0.3 to 7.0.2.

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.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[carlos-alm]

Reviewed this bump with extra scrutiny given it's a major version jump (6.x → 7.x) of the TypeScript compiler itself.

Conflicts: none (mergeable).

CI: red, and it is a genuine incompatibility, not flakiness. Every failing check (CI Testing Pipeline, Embedding regression tests, Engine parity ×3, Lint, Pre-publish benchmark gate, Test Node 22 ×3, TypeScript type check, Validate commits, impact) fails downstream of the same root cause: npm run build (tsc) fails with ~70 TS2339/TS2694/TS7006 errors, all confined to src/domain/graph/resolver/ts-resolver.ts.

Root cause: TypeScript 7.0 is the native/Go-ported compiler rewrite. Its package.json now maps the "." export to ./lib/version.cjs, which only exposes { version, versionMajorMinor }. The classic in-process Compiler API (ts.createProgram, ts.Program, ts.TypeChecker, ts.sys, ts.readConfigFile, ts.forEachChild, ts.isIdentifier, etc.) that ts-resolver.ts depends on for its TSC-based type enrichment pass (Phase 8.1) has been removed from the package entirely (confirmed: no readConfigFile/createProgram anywhere in the shipped lib//dist/). It's replaced by an out-of-process RPC client under typescript/unstable/sync//async that returns proxy objects (NodeHandle, Symbol, TypeObject) from a spawned compiler process — a different architecture, not a renamed API.

I verified this isn't just a type-check nuisance: at runtime (independent of the tsc failure), (await import('typescript')).default under TS 7 only has {version, versionMajorMinor}, so ts.readConfigFile is undefined. createProgram()'s try/catch swallows the resulting TypeError and returns null — no crash, but the entire TSC type-enrichment feature silently and permanently no-ops for any project using typescript@7+, with only a debug()-level trace.

Fixing this properly means redesigning ts-resolver.ts's TSC integration around the new client-server API (~70 call sites, spawning/managing a compiler process, NodeHandle/DocumentIdentifier lookups instead of direct AST walking) — a project of its own, not something to bundle into a dependency-bump PR.

Filed #2106 to track the redesign. Until that's done, recommend keeping typescript pinned below 7.0.0 — i.e. @dependabot ignore this major version on this PR.

Status: needs-human-review (not merging as-is).

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.