CODEWITHSUNDEEP
node.jswebpackwebpack-2
CWright
CWright

Reputation: 2098

Webpack2 node-libs-browser exclude?

I've upgraded to webpack 2 and before tree shaking my bundle size has increased. When investigating why it seems I have large files like bn.js and eliptic (some dependencies of node-libs-browser - which itself is now a dependency of webpack2). Is there any way to remove these or exclude them? In webpack1 they weren't being added to my bundle.

Upvotes: 10

Views: 2447

Answers (1)

Joel Chen
Joel Chen

Reputation: 278

The problem is because webpack by default applies its internal plugin NodeSourcePlugin here or here for webworker, and if you have a module that even references a NodeJS module like crypto, ie: var Crypto = canUseDom ? null : require("crypto"), webpack will bundle a bunch of big files to simulate NodeJS. See issue filed here https://github.com/webpack/webpack/issues/4976.

The solution is to avoid any code that references NodeJS internal modules, even if they are not used on the browser.

To catch these, you can remove NodeSourcePlugin by overriding the target option.

const webpack = require("webpack");
const FunctionModulePlugin = require("webpack/lib/FunctionModulePlugin");

const output = {
  path: process.cwd() + "/build",
  filename: "bundle.[hash].js"
};

{
  target: () => undefined,
  output,
  plugins: [
    new webpack.JsonpTemplatePlugin(output),
    new FunctionModulePlugin(output),
    new webpack.LoaderTargetPlugin("web"),
  ]
}

Edit: with webpack 3, it's now as simple as:

const webpackConfig = {
  node: false
}

If you must have code that's for server side only and references NodeJS modules, it's better to separate those into their own module, and export a dummy copy through the browser field in package.json.

Edit: I wrote a blog related to this issue here https://medium.com/walmartlabs/webpack-optimization-a-case-study-92b130334b6c.

Upvotes: 14

Related Questions