nuke-webpack-bundle-analyzer v0.1.0

npm install --save-dev @ali/nuke-webpack-bundle-analyzer

const BundleAnalyzerPlugin = require('@ali/nuke-webpack-bundle-analyzer')
  .BundleAnalyzerPlugin;

module.exports = {
  plugins: [new BundleAnalyzerPlugin()]
};

It will create an interactive treemap visualization of the contents of all your bundles.

This module will help you:

1. Realize what's really inside your bundle
2. Find out what modules make up the most of its size
3. Find modules that got there by mistake
4. Optimize it!

And the best thing is it supports minified bundles! It parses them to get real size of bundled modules. And it also shows their gzipped sizes!

new BundleAnalyzerPlugin(options?: object)

You can analyze an existing bundle if you have a webpack stats JSON file.

You can generate it using BundleAnalyzerPlugin with generateStatsFile option set to true or with this simple command:

webpack --profile --json > stats.json

If you're on Windows and using PowerShell, you can generate the stats file with this command to avoid BOM issues:

webpack --profile --json | Out-file 'stats.json' -Encoding OEM

Then you can run the CLI tool.

webpack-bundle-analyzer bundle/output/path/stats.json

webpack-bundle-analyzer <bundleStatsFile> [bundleDir] [options]

Arguments are documented below:

bundleStatsFile

Path to webpack stats JSON file

bundleDir

Directory containing all generated bundles.

options

  -h, --help                  output usage information
  -V, --version               output the version number
  -m, --mode <mode>           Analyzer mode. Should be `server` or `static`.
                              In `server` mode analyzer will start HTTP server to show bundle report.
                              In `static` mode single HTML file with bundle report will be generated.
                              Default is `server`.
  -h, --host <host>           Host that will be used in `server` mode to start HTTP server.
                              Default is `127.0.0.1`.
  -p, --port <n>              Port that will be used in `server` mode to start HTTP server.
                              Default is 8888.
  -r, --report <file>         Path to bundle report file that will be generated in `static` mode.
                              Default is `report.html`.
  -s, --default-sizes <type>  Module sizes to show in treemap by default.
                              Possible values: stat, parsed, gzip
                              Default is `parsed`.
  -O, --no-open               Don't open report in default browser automatically.

webpack-bundle-analyzer reports three values for sizes. defaultSizes can be used to control which of these is shown by default. The different reported sizes are:

stat

This is the "input" size of your files, before any transformations like minification.

It is called "stat size" because it's obtained from Webpack's stats object.

parsed

This is the "output" size of your files. If you're using a Webpack plugin such as Uglify, then this value will reflect the minified size of your code.

gzip

This is the size of running the parsed bundles/modules through gzip compression.

I can't see all the dependencies in a chunk

This is a known caveat when webpack.optimize.ModuleConcatenationPlugin is used with Webpack 3 or webpack-bundle-analyzer < 2.11.0. The way ModuleConcatenationPlugin works is that it merges multiple modules into a single one, and so that resulting module doesn't have edges anymore. Webpack 3 didn't provide any information about concatenated modules, but Webpack 4 started including it into a stats files and webpack-bundle-analyzer 2.11.0 learned to show it.

If for some reason you can't update to the latest versions try analyzing your bundle without ModuleConcatenationPlugin. See issue #115 for more discussion.

webpack analysis for @ali.