-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[Bug]: Script evaluation using babel-node’s ‘--eval’ doesn’t apply default config file #16675
Comments
Hey @Rinzwind! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly. If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite. |
Thank you for the report. It will be fixed in v7.25.0 by #16642. |
💻
How are you using Babel?
@babel/register or @babel/node
Input code
Configuration file name
babel.config.js
Configuration
Current and expected behavior
Using a file ‘test.js’ with the input code given above, and a file ‘babel.config.js’ with the given configuration which uses a plugin to replace
"foo"
by"bar"
, the following has the expected result:But when using
--eval
to pass the input code, the result is unexpected, the config file does not seem to be applied:Environment
Possible solution
No response
Additional context
Issue #11877, which is about
--config-file
not being applied, is similar but differs in that it says that a default config file did work.The text was updated successfully, but these errors were encountered: