-
Notifications
You must be signed in to change notification settings - Fork 33
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
Jest.mergePreset: Fix compatibility with NodeNext
#1481
Conversation
🦋 Changeset detectedLatest commit: 5eb6ea5 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
NodeNext
NodeNext
@@ -38,10 +63,8 @@ module.exports.transform = Object.fromEntries( | |||
TS_JEST_PATH, | |||
{ | |||
...value[1], | |||
isolatedModules: | |||
value[1]?.isolatedModules ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Removed some of this complexity because defaults.transform
doesn't populate isolatedModules
nor tsconfig
. We can always update this in future if that changes.
https://github.com/seek-oss/skuba/actions/runs/8338828529
Co-authored-by: Michael Taranto mtaranto@seek.com.au