JSPM

bundle-stats-webpack-plugin

4.12.0-beta.0
  • ESM via JSPM
  • ES Module Entrypoint
  • Export Map
  • Keywords
  • License
  • Repository URL
  • TypeScript Types
  • README
  • Created
  • Published
  • Downloads 41902
  • Score
    100M100P100Q157672F
  • License MIT

In-depth bundle analyzer for webpack(bundle size, assets, modules, packages)

Package Exports

  • bundle-stats-webpack-plugin
  • bundle-stats-webpack-plugin/lib/index.js

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (bundle-stats-webpack-plugin) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

BundleStats screenshot

Demos: Bundle analysis comparison ยท Bundle analysis

BundleStats webpack plugin

Analyze webpack stats(bundle size, assets, modules, packages) and compare the results between different builds.

Node version GitHub action CodeQL

RelativeCI

- Bundle size and totals by file type(css, js, img, etc)
- Insights: duplicate packages, new packages
- Initial JS/CSS, Cache invalidation, and other bundle metrics
- Assets report (entrypoint, initial, types, changed, delta)
- Modules report (changed, delta, chunks, duplicate count and percentage)
- Packages report (count, duplicate, changed, delta)
โญ Side by side comparison for multiple builds

Table of Contents

Install

npm install --dev bundle-stats-webpack-plugin

or

yarn add --dev bundle-stats-webpack-plugin

Webpack configuration

// webpack.config.js
const { BundleStatsWebpackPlugin } = require('bundle-stats-webpack-plugin');

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

BundleStatsWebpackPlugin(options)

  • compare - use local saved baseline for comparison (default true).
  • baseline - save current webpack stats as baseline (default false).
  • html - output html report (default true).
  • json - output json report (default false).
  • outDir - output directory relative to webpack output.path (default '').
  • baselineFilepath - baseline filepath relative to webpack output.path (default 'node_modules/.cache/bundle-stats/baseline.json')
  • silent - stop logging info and only log warning and error (default false).
  • stats - Webpack stats options default:
    {
      stats: {
        assets: true,
        chunks: true,
        modules: true,
        builtAt: true,
        hash: true
      }
    }

How to configure webpack for better debugging and monitoring

Use with create-react-app

You will need to customize the default webpack config. That can be done by using react-app-rewired which is one of create-react-app's custom config solutions. You will also need customize-cra.

npm install --dev customize-cra react-app-rewired

or

yarn add customize-cra react-app-rewired --dev

Change your default scripts in package.json to:

/* package.json */
"scripts": {
  "start": "react-app-rewired start",
  "build": "react-app-rewired build",
  "test": "react-app-rewired test"
}

Create a file config-overrides.js at the same level as package.json.

// config-overrides.js
const { override, addWebpackPlugin } = require('customize-cra');
const { BundleStatsWebpackPlugin } = require('bundle-stats-webpack-plugin');

module.exports = override(
  addWebpackPlugin(new BundleStatsWebpackPlugin()),
);

Compare mode

In compare mode, the metrics are compared against an existing(node_modules/.cache/bundle-stats/baseline.json) Webpack stats file(baseline). To generate the baseline webpack stats, set BUNDLE_STATS_BASELINE environmental variable to true or set BundleStatsWebpackPlugin baseline option to true:

# Checkout to the branch/tag/commit where you want to generate the baseline
$ git checkout master

# Build your application with BUNDLE_STATS_BASELINE environmental variable
$ BUNDLE_STATS_BASELINE=true npm run build

# Checkout to the working branch/tag/commit
$ git checkout MY_FEATURE_BRANCH

# Build your application
$ npm run build

The option can be disabled by setting BundleStatsWebpackPlugin compare option to false.

Other packages

bundle-stats

npm npm

CLI to generate bundle stats report.

gatsby-plugin-bundle-stats

npm npm

Gatsby plugin for bundle-stats.

next-plugin-bundle-stats

npm npm

Next.js plugin for bundle-stats.

rollup-plugin-bundle-stats

npm npm

Rollup plugin to generate bundle stats report.

๐ŸŒ€ relative-ci.com

Optimize your web app's performance with automated bundle stats analysis and monitoring.

  • ๐Ÿ”ฎ In-depth bundle stats analysis for every build
  • ๐Ÿ“ˆ Monitor bundle stats changes and identify opportunities for optimizations
  • ๐Ÿ”” Rule based automated review flow, or get notified via GitHub Pull Request comments, GitHub check reports and Slack messages
  • ๐Ÿ”ง Support for webpack and beta support for Vite/Rollup
  • ๐Ÿ”จ Support for all major CI services(CircleCI, GitHub Actions, Gitlab CI, Jenkins, Travis CI)
  • ๐Ÿ”ฉ Support for npm, yarn and pnpm; support for monorepos
  • ๐Ÿ’• Always free for Open Source

๐Ÿš€ Get started

๐ŸŒ“ relative-ci/compare

Standalone web application to compare Webpack/Lighthouse/Browsertime stats.

Compare bundle stats

โšก bundle-stats-action

Github Action that generates bundle-stats reports.