Socket
Socket
Sign inDemoInstall

babili-webpack-plugin

Package Overview
Dependencies
84
Maintainers
3
Versions
14
Alerts
File Explorer

Advanced tools

Install Socket

Detect and block malicious and high-risk dependencies

Install

    babili-webpack-plugin

Babili Plugin for Webpack


Version published
Weekly downloads
2.1K
decreased by-5.51%
Maintainers
3
Install size
6.86 MB
Created
Weekly downloads
 

Readme

Source

npm deps test coverage quality chat

Babili Webpack Plugin

A Webpack Plugin for Babili - A babel based minifier

Install

npm install babili-webpack-plugin --save-dev

Usage

// webpack.config.js
const BabiliPlugin = require("babili-webpack-plugin");
module.exports = {
  entry: //...,
  output: //...,
  plugins: [
    new BabiliPlugin(babiliOptions, overrides)
  ]
}

Options

babiliOptions

babiliOptions are passed on to the babili preset. Check https://github.com/babel/babili/tree/master/packages/babel-preset-babili#options. Default: {}.

Overrides
  • test: JS file extension regex. Default: /\.js($|\?)/i
  • 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. require("babel-core")
  • babili: Pass in a custom babili preset instead - require("babel-preset-babili"). ``

Why

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_modules from 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.

Maintainers


Boopathi Rajaa

Juho Vepsäläinen

Joshua Wiens

Kees Kluskens

Sean Larkin

Keywords

FAQs

Last updated on 26 Jun 2017

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc