-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
ci: use node 24 #5949
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
base: master
Are you sure you want to change the base?
ci: use node 24 #5949
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #5949 +/- ##
=======================================
Coverage 98.55% 98.55%
=======================================
Files 270 270
Lines 8718 8719 +1
Branches 1495 1496 +1
=======================================
+ Hits 8592 8593 +1
Misses 93 93
Partials 33 33 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Node24 is also the same as node 22.12.0. The error message is different from 22.11.0, which will cause the test to fail. rollup/.github/workflows/build-and-tests.yml Lines 501 to 503 in 02da7ef
In response to this situation, I modified the judgment condition of the test case. However, I am not sure whether this is appropriate. |
I wonder if the problem is the native support for requiring ES modules. Then maybe we need to skip the test Node >= 22, or run a different test instead. |
It seems that the warning messages given by the node when loading es module in versions 22.11.0 and 24.0.0 are different, resulting in different results of the following judgment logic, which leads to test failure. ref nodejs/node#56628 rollup/cli/run/loadConfigFile.ts Lines 63 to 67 in 7536ffb
|
This PR contains:
Are tests included? 8000 p>
Breaking Changes?
List any relevant issue numbers:
Description
https://github.com/nodejs/node/releases/tag/v24.0.0