Babili Webpack Plugin
A Webpack Plugin for Babili - A babel based minifier
npm install babili-webpack-plugin --save-dev
// webpack.config.jsconst BabiliPlugin = ;moduleexports =entry: //...,output: //...,plugins:babiliOptions overrides
babiliOptions are passed on to the babili preset. Check https://github.com/babel/babili/tree/master/packages/babel-preset-babili#options.
test: JS file extension regex. Default:
comments: Preserve Comments. Default:
/@preserve|@licen(s|c)e/. falsy value to remove all comments. Accepts function, object with property test (regex), and values.
sourceMap: Default: uses webpackConfig.devtool. Set this to override that.
parserOpts: Configure babel with special parser options.
babel: Pass in a custom babel-core instead.
babili: Pass in a custom babili preset instead -
You can also use babel-loader for webpack and include
babili as a preset and should be much faster than using this - as babili will operate on smaller file sizes. But then, why does this plugin exist at all? -
- A webpack loader operates on single files and babili preset as a webpack loader is going to consider each file to be executed directly in the browser global scope (by default) and will not optimize some things in the toplevel scope. This is going to change and you can opt-in to optimize toplevel scope - babel/babili#210, babel/babili#203, etc...
- When you exclude
node_modulesfrom being run through the babel-loader, babili optimizations are not applied to the excluded files as it doesn't pass through the minifier.
- When you use the babel-loader with webpack, the code generated by webpack for the module system doesn't go through the loader and is not optimized by babili.
- A webpack plugin can operate on the entire chunk/bundle output and can optimize the whole bundle and you can see some differences in minified output. But this will be a lot slower as the file size is usually really huge. So there is another idea where we can apply some optimizations as a part of the loader and some optimizations in a plugin.