chore(deps): update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	^5.7.0 → ^6.0.0

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[doubleword-code]

Summary

This PR updates the TypeScript dev dependency from ^5.7.0 to ^6.0.0 in the TypeScript SDK. The change is straightforward: it bumps the version in package.json and updates package-lock.json accordingly. The codebase is well-positioned for this upgrade because the tsconfig.json already explicitly configures all compiler options that changed defaults in TypeScript 6.0 (e.g., strict: true, rootDir: "src", moduleResolution: "bundler").

Verdict: Approved pending verification that CI passes. No code changes are required, but the CI workflow should be run to confirm type checking and build succeed with TypeScript 6.0.

Research notes

Fetched the TypeScript 6.0 announcement blog and GitHub release notes. Key breaking changes in TS 6.0 include:

• strict now defaults to true (this repo already sets it explicitly)
• types now defaults to [] instead of auto-including all @types/* packages (not applicable here — the project uses explicit imports)
• rootDir now defaults to . instead of being inferred (this repo explicitly sets "rootDir": "src")
• moduleResolution: node / node10 is deprecated (this repo uses "bundler")
• New inference rules for function expressions in generic calls (may require explicit type arguments in edge cases)
• Various deprecated options removed (outFile, baseUrl as lookup root, amd/umd/systemjs module targets, etc.)

None of these deprecations affect this codebase based on the current tsconfig.json configuration.

Suggested next steps

1. Run CI to verify type checking passes — The CI workflow (npm run typecheck and npm run build) should be executed to confirm there are no new type errors under TypeScript 6.0's stricter inference rules.
2. Monitor for subtle inference changes — TypeScript 6.0 has updated inference for function expressions in generic contexts. If CI fails, look for errors around generic calls that may need explicit type arguments.
3. Consider testing with TypeScript 7.0 native preview — Since TS 6.0 is a bridge release to TS 7.0 (the native Go port), consider testing against the TS 7.0 preview to identify any forward-compatibility issues early.

General findings

• The package-lock.json changes show removal of "peer: true" from the esbuild and typescript entries. This is normal npm metadata cleanup and has no functional impact.
• The bin entry for autobatcher appears in the lockfile diff because it was added to package.json in a prior commit — this is just reflecting the actual state of package.json.
• The codebase follows modern TypeScript practices (explicit imports, ESM, bundler module resolution) which aligns well with TypeScript 6.0's direction.

---

Overall assessment: This is a low-risk dependency update. The project's explicit tsconfig.json configuration shields it from TypeScript 6.0's breaking default changes. Approval is recommended contingent on CI passing.

[doubleword-code]

Summary

This PR updates the TypeScript SDK's devDependency from typescript: ^5.7.0 to typescript: ^6.0.0. After reviewing the codebase against TypeScript 6.0's breaking changes and deprecations, the project appears well-configured for this upgrade.

Verdict: Ready to merge with one optional hardening suggestion.

Research notes

Fetched the official TypeScript 6.0 announcement blog post to identify breaking changes that could affect this codebase:

• strict defaults to true — Project already has explicit "strict": true ✓
• rootDir defaults to . — Project has explicit "rootDir": "src" ✓
• types defaults to [] — Project does NOT have explicit types field (see Non-blocking finding)
• Deprecated: asserts keyword — Codebase uses no import assertions ✓
• Deprecated: legacy module syntax for namespaces — No namespace declarations found ✓
• Deprecated: /// <reference no-default-lib> — No reference directives found ✓

The package-lock.json changes (removing "peer": true from esbuild/typescript entries) reflect npm's updated peer dependency tracking in TS 6.0 era — this is expected and harmless.

Suggested next steps

1. (Optional) Add explicit "types": ["node"] to typescript/tsconfig.json to make the global type dependency explicit and improve build performance/predictability per TS 6.0 best practices.
2. Run npm run typecheck and npm run build locally after merging to confirm no regressions (CI will also validate this).

General findings

No blocking issues identified. The codebase follows modern TypeScript patterns and avoids deprecated features. The explicit configuration in tsconfig.json shields the project from most TS 6.0 breaking changes.

[doubleword-code]

Non-blocking: Consider adding an explicit "types" field to tsconfig.json to align with TypeScript 6.0 best practices.

Why it matters: TypeScript 6.0 changed the default for types from auto-including all @types/* packages to an empty array []. While your project has "skipLibCheck": true which mitigates most issues, explicitly declaring "types": ["node"] makes the global type dependency clear and improves build performance by avoiding unnecessary type loading.

Suggested fix: Add to typescript/tsconfig.json:

{
  "compilerOptions": {
    "types": ["node"],
    // ... rest of options
  }
}

This is also recommended by the TypeScript 6.0 migration guide.