feat: allow config transpiling (babel, typescript, etc) #6
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.
This PR contains:
Breaking Changes?
If yes, please describe the breakage.
Please Describe Your Changes
Fixes #5. Introduces support for transpiling webpack configs on the fly. This allows users to use babel (webpack.config.babel.js, webpack.config.es6), typescript (webpack.config.ts), and other module loaders to write their webpack configs. Users are responsible for installing the necessary dependency(s) for the module loader that matches their file type.
This is the full list of file extensions supported, along with the loaders looked for when using a file type in this list:
If a config file type is used which is not in that list, the Node
require
pipeline will attempt to load the file. If a module loader is not installed for a special file type, webpack-nano will throw an error.