npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

rollup-plugin-bundle-analyzer

v1.6.6

Published

rollup plugin that represents bundle content as convenient interactive zoomable treemap

Readme

# NPM
npm install --save-dev rollup-plugin-bundle-analyzer
# Yarn
yarn add -D rollup-plugin-bundle-analyzer
import bundleAnalyzer from "rollup-plugin-bundle-analyzer";


plugins: [
    bundleAnalyzer(),
    vue(),
]

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

rollup 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!

bundleAnalyzer(options?: object)

|Name|Type|Description| |:--:|:--:|:----------| |analyzerMode|One of: server, static, json | 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. |host|{String}|Default: 127.0.0.1. Host that will be used in server mode to start HTTP server.| |port|{Number} or auto|Default: 9800. Port that will be used in server mode to start HTTP server.| |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 | |generateStatsFile|{Boolean}|Default: false. If true, rollup stats JSON file will be generated in bundle output directory| |statsFilename|{String}|Default: stats.json. Name of rollup 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 | |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. |

input

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

render

This is the "output" size of your files. If you're using a rollup 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.

When opened, the report displays all of the 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