chore(deps): update dependency typescript to v6

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript (source)	5.9.3 → 6.0.2

---

Release Notes

microsoft/TypeScript (typescript)

v6.0.2

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday (* 0-4,22-23 * * 1-5)
  • Only on Sunday and Saturday (* * * * 0,6)
• 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]

Renovate PR Review Results

⚖️ Safety Assessment: ✅ Safe

🔍 Release Content Analysis

Major TypeScript 6.0 Release (March 23, 2026)

• TypeScript 6.0 is the final JavaScript-based release before TypeScript 7.0 (which will be rewritten in Go)
• Version 6.0.2 is a stable patch release following 6.0.0 Beta and 6.0.1 RC

Significant Breaking Changes:

• Removed Options: target: es5 (deprecated, minimum now ES2015), --moduleResolution classic (removed entirely), --downlevelIteration (no longer supported), legacy module formats (amd, umd, systemjs, none), --outFile (deprecated)
• Forced Settings: esModuleInterop and allowSyntheticDefaultImports can no longer be set to false (safer interop always enabled), --alwaysStrict false no longer supported
• Default Changes: target defaults to ES2025 (was ES3), module defaults to ESNext (was CommonJS), moduleResolution defaults to bundler when module is ESNext, types defaults to empty array [] (was auto-enumerate all @types)
• CLI Behavior: Running tsc with file arguments when tsconfig.json exists now errors

New Features:

• Enhanced type inference for functions without explicit this usage
• Subpath imports now support #/ prefix syntax
• --moduleResolution bundler can combine with --module commonjs
• New built-in types for es2025 target (RegExp.escape, Temporal APIs, Map/WeakMap upsert methods)
• --stableTypeOrdering flag for identifying ordering differences with TypeScript 7.0

Security Fixes:

• No specific security vulnerabilities fixed in 6.0.2 patch

🎯 Impact Scope Investigation

Package Usage Location:

• internal/sandbox/defaults/node-typescript/package.json - TypeScript dependency for the node-typescript runtime
• internal/sandbox/defaults/node-typescript/tsconfig.json - Compilation configuration
• Docker build at line 38-39 - TypeScript installed into /mise/ts-node-modules/ via npm ci

Current Configuration Analysis:
The existing tsconfig.json at internal/sandbox/defaults/node-typescript/tsconfig.json is:

{
  "compilerOptions": {
    "target": "ES2024",
    "module": "commonjs",
    "lib": ["ES2024"],
    "esModuleInterop": true,
    "skipLibCheck": true
  }
}

Compatibility Assessment:

• ✅ target: ES2024 - Fully compatible (ES2015+ required, ES2024 is valid)
• ✅ module: commonjs - Still supported in TypeScript 6.0
• ✅ esModuleInterop: true - Already enabled, matches TypeScript 6.0 forced behavior
• ✅ lib: ["ES2024"] - Valid library target
• ⚠️ Missing moduleResolution - Will now default to bundler in TS 6.0 (previously defaulted to node10), but this shouldn't break compilation since the sandbox compiles isolated TypeScript files without external module resolution

Runtime Usage:

• TypeScript is used exclusively for the node-typescript runtime compilation step
• Compilation command: /mise/installs/node/current/bin/node --disable-wasm-trap-handler /sandbox/node_modules/typescript/bin/tsc
• Pre-installed in Docker image as read-only bind mount at /sandbox/node_modules
• No custom TypeScript API usage - only CLI invocation via tsc

Impact on Dependencies:

• @types/node version 24.12.2 remains unchanged - no compatibility issues
• No other dependencies affected
• TypeScript is dev-only and runs during sandbox compilation, not in user code

E2E Test Coverage:
Comprehensive test suite exists at e2e/tests/runtime/node-typescript.yml covering:

• Basic compilation and execution
• Compile errors (type errors, syntax errors)
• Multiple files with imports
• Interfaces, generics, enums, async/await
• Custom tsconfig.json overrides
• Standard library usage

💡 Recommended Actions

Immediate Actions:

1. ✅ Merge is safe - The update maintains backward compatibility for this codebase's usage
2. ⚠️ Consider adding explicit moduleResolution - While not strictly required for the sandbox's use case (compiling isolated user files), adding "moduleResolution": "node" to tsconfig.json would make the configuration more explicit and prevent future confusion

Testing Recommendations:

1. Run existing E2E tests after merge: docker compose down && docker compose up --build -d && go test -tags e2e ./e2e/...
2. Verify all test cases in e2e/tests/runtime/node-typescript.yml pass
3. No code changes required - TypeScript 6.0's breaking changes don't affect the current configuration

Post-Merge Monitoring:

• Monitor for any TypeScript compilation errors in the node-typescript runtime
• Watch for error message format changes that might affect E2E test regex patterns (particularly in e2e/tests/runtime/node-typescript.yml lines 45-70 for error output matching)

Optional Enhancement (Not Required for Merge):

{
  "compilerOptions": {
    "target": "ES2024",
    "module": "commonjs",
    "moduleResolution": "node",  // Make explicit to avoid TS 6.0 default change
    "lib": ["ES2024"],
    "esModuleInterop": true,
    "skipLibCheck": true
  }
}

🔗 Reference Links

• Announcing TypeScript 6.0
• TypeScript 6.0 Documentation
• TypeScript 5.x to 6.0 Migration Guide
• TypeScript 6.0 Releases
• Renovate PR #43 Diff

Generated by koki-develop/claude-renovate-review