Skip to content

chore: migrate to TypeScript 6.0#337

Open
goloroden wants to merge 1 commit intomainfrom
claude/typescript-6-0-review-SHfJP
Open

chore: migrate to TypeScript 6.0#337
goloroden wants to merge 1 commit intomainfrom
claude/typescript-6-0-review-SHfJP

Conversation

@goloroden
Copy link
Member

Summary

  • Update TypeScript from 5.9.3 to 6.0.2 (last JS-based release before the Go rewrite in TS 7.0)
  • Remove deprecated baseUrl option and migrate absolute imports (src/types/...) to relative imports (../types/...) in 4 stream files
  • Remove esModuleInterop: true — always enabled in TS 6.0, no longer configurable
  • Change module from CommonJS to preserve — tsup handles the actual bundling
  • Add moduleResolution: bundler — the implicit node10 default is deprecated
  • Add types: ["node"] — new default is [], which would break Node.js global type resolution
  • Add ignoreDeprecations: "6.0" — needed because tsup internally uses baseUrl for DTS generation (can be removed once tsup ships a TS 6.0-compatible update)

Test plan

  • npm run analyze passes (type-checking + biome linting)
  • npm run build produces dist/index.js, dist/index.mjs, dist/index.d.ts
  • npm run test passes (requires EventSourcingDB container)
  • No new TypeScript deprecation warnings

https://claude.ai/code/session_0168r2kkTqkaA39YaV2XPVac

- Update typescript from 5.9.3 to 6.0.2
- Remove deprecated baseUrl option (migrate absolute imports to relative)
- Remove esModuleInterop (always enabled in TS 6.0)
- Change module from CommonJS to preserve (tsup handles bundling)
- Add explicit moduleResolution: bundler (node10 deprecated)
- Add explicit types: ["node"] (default changed to [])
- Add ignoreDeprecations: "6.0" (needed for tsup's internal baseUrl usage)

https://claude.ai/code/session_0168r2kkTqkaA39YaV2XPVac
@goloroden goloroden requested a review from a team as a code owner March 24, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants