webpack-bundle-analyzer vs webpack-dashboard
Webpack Visualization Tools Comparison
Search packages..
1 Year
webpack-bundle-analyzerwebpack-dashboardSimilar Packages:
What's Webpack Visualization Tools?

Webpack visualization tools are essential for developers to understand the structure and performance of their bundled assets in a Webpack project. These tools provide insights into the size, composition, and dependencies of JavaScript bundles, helping developers optimize their applications by identifying large modules, unused code, and potential improvements in load times. By visualizing the bundle, developers can make informed decisions on how to split code, manage dependencies, and enhance overall performance, leading to a better user experience and more efficient applications.

Package Weekly Downloads Trend
Github Stars Ranking
Stat Detail
Package
Downloads
Stars
Size
Issues
Publish
License
webpack-bundle-analyzer6,976,51012,6281.23 MB31a year agoMIT
webpack-dashboard28,54513,85952.2 kB392 years agoMIT
Feature Comparison: webpack-bundle-analyzer vs webpack-dashboard

Visualization

  • webpack-bundle-analyzer:

    webpack-bundle-analyzer provides an interactive treemap visualization of the contents of your bundles. This allows developers to see the size of each module and its dependencies, making it easier to identify large modules and optimize them effectively.

  • webpack-dashboard:

    webpack-dashboard offers a real-time dashboard that displays build progress, warnings, and errors in a more user-friendly manner. It focuses on providing a quick overview of the build process rather than detailed insights into bundle composition.

Use Case

  • webpack-bundle-analyzer:

    Ideal for projects where understanding the bundle size and composition is critical for performance optimization. It is particularly useful for large applications with many dependencies, as it helps in identifying which modules are bloating the bundle.

  • webpack-dashboard:

    Best suited for developers who want a streamlined experience during development. It enhances the feedback loop by providing real-time updates on the build process, making it easier to catch errors and warnings as they occur.

Integration

  • webpack-bundle-analyzer:

    Easily integrates with Webpack configurations and can be run as a plugin or in the command line. It can generate reports in various formats, including HTML, JSON, and CSV, allowing for flexible usage in different environments.

  • webpack-dashboard:

    Integrates seamlessly with Webpack's development server, providing a live view of the build process. It is less about analyzing bundles and more about improving the developer experience during the build.

Customization

  • webpack-bundle-analyzer:

    Highly customizable, allowing developers to filter and sort modules based on size, name, or other criteria. It also supports various configurations to tailor the analysis to specific needs, such as excluding certain modules from the report.

  • webpack-dashboard:

    Offers limited customization options, focusing primarily on displaying build information. Its main goal is to enhance the visibility of the build process rather than provide extensive configuration options.

Learning Curve

  • webpack-bundle-analyzer:

    Requires some understanding of Webpack and its configuration to leverage its full potential. However, once set up, it provides valuable insights that can significantly improve development practices.

  • webpack-dashboard:

    Very easy to set up and use, making it accessible for developers of all skill levels. It provides immediate feedback without requiring deep knowledge of Webpack internals.

How to Choose: webpack-bundle-analyzer vs webpack-dashboard
  • webpack-bundle-analyzer:

    Choose webpack-bundle-analyzer if you need a detailed analysis of your Webpack bundles, including visual representation through interactive treemaps. It helps identify the size of each module and its impact on the overall bundle size, making it easier to pinpoint areas for optimization.

Similar Npm Packages to webpack-bundle-analyzer

webpack-bundle-analyzer is a powerful tool that helps developers visualize the size of their webpack output files with an interactive treemap. This tool provides insights into the composition of your bundles, making it easier to identify large dependencies and optimize your application's performance. By analyzing the bundle size, developers can make informed decisions about code splitting, lazy loading, and other optimization techniques.

While webpack-bundle-analyzer is a popular choice for analyzing bundle sizes, there are several alternatives that offer similar functionalities. Here are a few noteworthy options:

  • bundlewatch is a tool designed to monitor the size of your bundles over time. It allows you to set size limits for your bundles and will notify you if any of them exceed the specified limits. This is particularly useful for maintaining performance standards in large projects and ensuring that new changes do not inadvertently bloat the bundle size.
  • source-map-explorer is a tool that analyzes JavaScript source maps to provide insights into the size of your JavaScript files. It helps you understand which parts of your code contribute to the overall bundle size, making it easier to identify and eliminate unnecessary code. This tool is especially useful for projects that use minification and bundling techniques.
  • stats-webpack-plugin is a webpack plugin that generates a JSON file containing information about the output files. This plugin can be used in conjunction with other tools to analyze the bundle size and structure. It provides a comprehensive overview of the build process, making it easier to debug and optimize your webpack configurations.
  • webpack-dashboard is a tool that provides a visual representation of your webpack build process in the terminal. While it does not focus solely on bundle size analysis, it offers real-time feedback on build performance, allowing developers to identify bottlenecks and optimize their build process.
  • webpack-visualizer-plugin is a plugin that generates a visual representation of your webpack bundle. It creates an HTML file that displays the size of each module in your bundle, helping you understand the structure and size distribution of your code. This tool is useful for quickly identifying large modules and optimizing your bundle.

To see how webpack-bundle-analyzer compares with these alternatives, check out the comparison: Comparing bundlewatch vs source-map-explorer vs stats-webpack-plugin vs webpack-bundle-analyzer vs webpack-dashboard vs webpack-visualizer-plugin.

Similar Npm Packages to webpack-dashboard

webpack-dashboard is a tool designed to provide a more user-friendly and visually appealing interface for monitoring the progress of Webpack builds. It enhances the command-line experience by presenting build statistics and logs in a dashboard format, making it easier for developers to track the status of their builds in real-time. This can be particularly useful in large projects where build times can be significant, allowing developers to quickly identify issues and optimize their build process.

While webpack-dashboard offers a great way to visualize build progress, there are alternatives that also provide insights into Webpack bundles. One notable alternative is:

  • webpack-bundle-analyzer. This tool provides a visual representation of the size of Webpack output files with an interactive zoomable treemap. It helps developers understand the composition of their bundles, identify large dependencies, and optimize their applications by reducing bundle size. By analyzing the bundle, developers can make informed decisions about code splitting, lazy loading, and other performance optimizations. If your primary goal is to analyze and optimize your bundle size rather than just monitor build progress, webpack-bundle-analyzer is an excellent choice.

To see how webpack-dashboard compares with webpack-bundle-analyzer, check out the comparison: Comparing webpack-bundle-analyzer vs webpack-dashboard.

README for webpack-bundle-analyzer

npm node tests downloads

Webpack Bundle Analyzer

Visualize size of webpack output files with an interactive zoomable treemap.

Install

# NPM
npm install --save-dev webpack-bundle-analyzer
# Yarn
yarn add -D webpack-bundle-analyzer

Usage (as a plugin)

const BundleAnalyzerPlugin = require('webpack-bundle-analyzer').BundleAnalyzerPlugin;

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

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

webpack bundle analyzer zoomable treemap

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!

Options (for plugin)

new BundleAnalyzerPlugin(options?: object)

|Name|Type|Description| |:--:|:--:|:----------| |analyzerMode|One of: server, static, json, disabled|Default: server. In server mode analyzer will start HTTP server to show bundle report. In static mode single HTML file with bundle report will be generated. In json mode single JSON file with bundle report will be generated. In disabled mode you can use this plugin to just generate Webpack Stats JSON file by setting generateStatsFile to true. | |analyzerHost|{String}|Default: 127.0.0.1. Host that will be used in server mode to start HTTP server.| |analyzerPort|{Number} or auto|Default: 8888. Port that will be used in server mode to start HTTP server. If analyzerPort is auto, the operating system will assign an arbitrary unused port | |analyzerUrl|{Function} called with { listenHost: string, listenHost: string, boundAddress: server.address}. server.address comes from Node.js| Default: http://${listenHost}:${boundAddress.port}. The URL printed to console with server mode.| |reportFilename|{String}|Default: report.html. Path to bundle report file that will be generated in static mode. It can be either an absolute path or a path relative to a bundle output directory (which is output.path in webpack config).| |reportTitle|{String\|function}|Default: function that returns pretty printed current date and time. Content of the HTML title element; or a function of the form () => string that provides the content.| |defaultSizes|One of: stat, parsed, gzip|Default: parsed. Module sizes to show in report by default. Size definitions section describes what these values mean.| |openAnalyzer|{Boolean}|Default: true. Automatically open report in default browser.| |generateStatsFile|{Boolean}|Default: false. If true, webpack stats JSON file will be generated in bundle output directory| |statsFilename|{String}|Default: stats.json. Name of webpack stats JSON file that will be generated if generateStatsFile is true. It can be either an absolute path or a path relative to a bundle output directory (which is output.path in webpack config).| |statsOptions|null or {Object}|Default: null. Options for stats.toJson() method. For example you can exclude sources of your modules from stats file with source: false option. See more options here. | |excludeAssets|{null\|pattern\|pattern[]} where pattern equals to {String\|RegExp\|function}|Default: null. Patterns that will be used to match against asset names to exclude them from the report. If pattern is a string it will be converted to RegExp via new RegExp(str). If pattern is a function it should have the following signature (assetName: string) => boolean and should return true to exclude matching asset. If multiple patterns are provided asset should match at least one of them to be excluded. | |logLevel|One of: info, warn, error, silent|Default: info. Used to control how much details the plugin outputs.|

Usage (as a CLI utility)

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

Options (for CLI)

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

Arguments are documented below:

bundleStatsFile

Path to webpack stats JSON file

bundleDir

Directory containing all generated bundles.

options

  -V, --version               output the version number
  -m, --mode <mode>           Analyzer mode. Should be `server`, `static` or `json`.
                              In `server` mode analyzer will start HTTP server to show bundle report.
                              In `static` mode single HTML file with bundle report will be generated.
                              In `json` mode single JSON file with bundle report will be generated. (default: server)
  -h, --host <host>           Host that will be used in `server` mode to start HTTP server. (default: 127.0.0.1)
  -p, --port <n>              Port that will be used in `server` mode to start HTTP server. Should be a number or `auto` (default: 8888)
  -r, --report <file>         Path to bundle report file that will be generated in `static` mode. (default: report.html)
  -t, --title <title>         String to use in title element of html report. (default: pretty printed current date)
  -s, --default-sizes <type>  Module sizes to show in treemap by default.
                              Possible values: stat, parsed, gzip (default: parsed)
  -O, --no-open               Don't open report in default browser automatically.
  -e, --exclude <regexp>      Assets that should be excluded from the report.
                              Can be specified multiple times.
  -l, --log-level <level>     Log level.
                              Possible values: debug, info, warn, error, silent (default: info)
  -h, --help                  output usage information

Size definitions

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.

Selecting Which Chunks to Display

When opened, the report displays all of the Webpack chunks for your project. It's possible to filter to a more specific list of chunks by using the sidebar or the chunk context menu.

Sidebar

The Sidebar Menu can be opened by clicking the > button at the top left of the report. You can select or deselect chunks to display under the "Show chunks" heading there.

Chunk Context Menu

The Chunk Context Menu can be opened by right-clicking or Ctrl-clicking on a specific chunk in the report. It provides the following options:

  • Hide chunk: Hides the selected chunk
  • Hide all other chunks: Hides all chunks besides the selected one
  • Show all chunks: Un-hides any hidden chunks, returning the report to its initial, unfiltered view

Troubleshooting

I don't see gzip or parsed sizes, it only shows stat size

It happens when webpack-bundle-analyzer analyzes files that don't actually exist in your file system, for example when you work with webpack-dev-server that keeps all the files in RAM. If you use webpack-bundle-analyzer as a plugin you won't get any errors, however if you run it via CLI you get the error message in terminal:

Error parsing bundle asset "your_bundle_name.bundle.js": no such file
No bundles were parsed. Analyzer will show only original module sizes from stats file.

To get more information about it you can read issue #147.

Other tools

  • Statoscope - Webpack bundle analyzing tool to find out why a certain module was bundled (and more features, including interactive treemap)

Maintainers


Yuriy Grunin
Vesa Laakso

Contributing

Check out CONTRIBUTING.md for instructions on contributing :tada:

npm-compare.com is an independent website designed to help developers choose the most suitable npm packages. We are not affiliated with npm, Inc or npmjs.com, the official website for the npm registry. Please note that npm is a registered trademark of npm, Inc. For more details, please refer to our Terms & Privacy.