-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add module: 'ES2022'
, support newer moduleResolution
kinds, support cts
+ mts
#447
Conversation
- updating dependencies
…ing bundler to node16
module: 'ES2022'
, update moduleResolution
default to node16
, add cts
+ `mts
module: 'ES2022'
, update moduleResolution
default to node16
, add cts
+ `mtsmodule: 'ES2022'
, update moduleResolution
default to node16
, add cts
+ mts
Replaced by #453 |
Or rather, this got split into multiple PRs it looks like:
Much nicer and easier to read as separate PRs! |
module: 'ES2022'
, update moduleResolution
default to node16
, add cts
+ mts
module: 'ES2022'
, support moduleResolution
overrides, support cts
+ mts
module: 'ES2022'
, support moduleResolution
overrides, support cts
+ mts
module: 'ES2022'
, support newer moduleResolution
kinds, support cts
+ mts
Yeah, ignore that PR, I started too many changes at once and updated deps too far and that required yet more changes and so on (we'd still have to figure out ts-jest problems eventually I guess). All interesting changes are pulled out into those 3 PRs |
Ah right, EDIT: welp, that gives even more problems because some of the test code does not work in ESM mode (e.g. |
Summary
Fix for #437
Details
moduleResolution
option as is ("node", "node16", "nodenext")