support ESM babel configs #4
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Released in https://github.com/node-loader/node-loader-babel/releases/tag/v1.1.0. I did a follow up commit in c0ae976 to expand isBabelConfig to support commonjs file extensions, too |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Babel can load ES module config files (
.babelrc.js,babel.config.js), but only when it is used asynchronously. This PR implements that.When loading an ESM config file, Babel uses dynamic
import(), which means the config file itself will also be passed to@node-loader/babel. We cannot transform a config file with babel, since we need the config file to know what to do in the first place. So possibly-ESM babel config files must be ignored by the loader.Thanks!