You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, all the other files are still compiled. This means that if my build script is babel src -d out, if I have two files (src/main.js and src/dep.js) and I run
BABEL_SHOW_CONFIG_FOR=./src/main.js npm run build
I will get an out folder containing only the dep.js file.
Either Babel should compile everything, or nothing.
I think the best thing to do would be to still compile the file, so that BABEL_SHOW_CONFIG_FOR only has effect on logging and on nothing else. However, I would be open to ignoring everything.
Bug Report
Current behavior
When using
BABEL_SHOW_CONFIG_FOR
, the file for which Babel is logging the config is considered as ignored and it's not compiled/handled:babel/packages/babel-core/src/config/config-chain.js
Line 266 in cb30c1d
However, all the other files are still compiled. This means that if my build script is
babel src -d out
, if I have two files (src/main.js
andsrc/dep.js
) and I runI will get an
out
folder containing only thedep.js
file.If you want to see this behavior, you can clone https://github.com/nicolo-ribaudo/babel-bug-show-config-behavior and run
BABEL_SHOW_CONFIG_FOR=./src/main.js npm run build
.Expected behavior
Either Babel should compile everything, or nothing.
I think the best thing to do would be to still compile the file, so that
BABEL_SHOW_CONFIG_FOR
only has effect on logging and on nothing else. However, I would be open to ignoring everything.Additional context
Thanks @laurieontech for the feedback!
The text was updated successfully, but these errors were encountered: