-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
feat(runtime): use compileFunction
over new Script
#15461
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for jestjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
'__tests__/b.test.js': "test('b', () => console.log('b'));", | ||
'package.json': JSON.stringify({jest: {testEnvironment: 'jsdom'}}), | ||
}); | ||
onNodeVersions('> 16', () => { |
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.
this is unfortunate, but hopefully most people have moved on from node 16 😀
Co-authored-by: Gareth Jones <Jones258@Gmail.com>
The following CI checks should also be removed in this case: |
Also: there's a line in the changelog about dropped node versions. v16 should be added to the list |
Summary
Reapplies and closes #12205.
Node 16 still has issues (and I don't intend to drop it for Jest 30), but most people are deffo on newer versions than that
Test plan
CI?