Skip to content

Upgrade TypeScript to 6.0 - #28

Closed
kac-axelor wants to merge 1 commit into
axelor:devfrom
kac-axelor:typescript-6.0-upgrade
Closed

kac-axelor wants to merge 1 commit into
axelor:devfrom
kac-axelor:typescript-6.0-upgrade

Conversation

@kac-axelor

@kac-axelor kac-axelor commented Jun 10, 2026 •

Copy link
Copy Markdown
Contributor

Bumps typescript ^5.9.3 → ^6.0.3.

The only change 6.0 forces on this repo is types: ["node"] in tsconfig — 6.0 stops auto-including everything under node_modules/@types, and the source relies on @types/node (Buffer, process, node:* modules). The config was already compliant otherwise: module: ESNext with bundler resolution, explicit strict and interop flags, no removed options.

Verified: tsc reports the identical four pre-existing errors as under 5.9 (untracked runtime-test issues — two of them are the nested-create sites fixed by the mappedBy PR); unit tests and the rslib build (including d.ts emission) pass unchanged. CI needs no changes.

Known behavioral note: 6.0 infers the exact argument shape for generics (microsoft/TypeScript#63515), so unknown keys nested inside where/select/create are silently accepted. This is surfaced by the type tests in #27 and fixed by the follow-up Options<> guard PR.


Series (merge order): #27 type tests (red by design) → #28 TypeScript 6.0 upgrade → #29 Options<> guard fix → #30 mappedBy fix. The suite in #27 goes fully green once all four are merged.

TS 6.0 no longer auto-includes node_modules/@types, so declare
types: ["node"] explicitly for the Buffer/process/node:* usage.
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.

1 participant