-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
fix: CI with Node v23.1.0 #16932
fix: CI with Node v23.1.0 #16932
Conversation
Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/58246 |
Did you mean |
Oops, I meant v23.1.0. |
Co-authored-by: Nicolò Ribaudo <nicolo.ribaudo@gmail.com>
...process.env, | ||
NODE_OPTIONS: | ||
parseInt(process.versions.node) >= 23 | ||
? "--disable-warning=ExperimentalWarning" |
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.
Does node 23.1 updated the error message? We already removed the experimental warning from stderr.
Plus if we provide other NODE_OPTIONS, this will replaced the provided options and with --disable-warning
only.
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.
You can see the failure at https://github.com/babel/babel/actions/runs/11509402711/job/32039492498 (commit: dd4ad48)
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.
I see, so node.js 23.1 updated the experimental warning: now they will print which file imports which module:
ExperimentalWarning: CommonJS module /home/runner/work/babel/babel/packages/babel-core/lib/config/files/module-types.js is loading ES Module /home/runner/work/babel/babel/packages/babel-core/test/fixtures/async/preset-mjs-native/preset.mjs using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Could have updated the experimental warning regex so we will not accidentally miss unwanted experimental warnings.
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.
Could you open another PR? 🙏
This reverts commit 8b5b6bf.
* Revert "fix: CI with Node v23.1.0 (babel#16932)" This reverts commit 8b5b6bf. * update known experimental warning regex
Fixes #1, Fixes #2