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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@chuyik/webpack-stats-diff

v1.6.3

Published

CLI tool to report changes in bundle sizes across builds

Downloads

22

Readme

webpack-stats-diff

A command-line tool to report changes in bundle sizes across builds.

The problem

You just made changes to your webpack config or your source files and you want to know how bundle sizes were impacted.

The solution

Use this tool to see how much the total built file size has changed and see the breakdown for what files were added or removed as well as what files increased or decreased in size.

Installation & Usage

Install with npm install -g webpack-stats-diff

To compare your bundle sizes before and after, you'll need to configure webpack to save a stats file. This can be done by either adding a script to your package.json similar to build_stats: webpack mode=production --json > stats.json or by adding webpack-stats-plugin into your plugins list.

For example, to compare the bundle sizes between branches, you could save the master build stats to a file master.json and the branch build stats to my-branch.json and run

webpack-stats-diff master.json my-branch.json
# options
# [--type terminal|markdown|wechat-work]
# [--extensions js,jsx]
# [--threshold 5]

terminal showing the result of running the command

Other Solutions

  • webpack-compare instead generates an HTML file to display the comparison, but it doesn't include totals or filtering options.