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

webpack-chunk-compare

v0.0.6

Published

Commandline util for comparing chunk modules from webpack stat json. Usage: wcmp a.json b.json

Downloads

20

Readme

Whoami

Commandline util for comparing chunk modules between two webpack stat json files. Basic Usage:

wcmp a.json b.json

Can I come over?

Installation is pretty easy:

npm install -g webpack-chunk-compare

Use me!

wcmp path/to/a/a.json path/to/a/b.json

What you get

--------------------
--  Contacts
--------------------

What "b" have that "a" doesn't
--------------
[ './special-lib.js' ]

What "a" have that "b" doesn't.
--------------
[]

--------------------
--  Common
--------------------

What "b" have that "a" doesn't
--------------
[]
What "a" have that "b" doesn't.
--------------
[ './lodash.js' ]

Use cases

  • Detecting why our chunk sizes changed in regards to previous project version.
  • Reviewing new modules.

Requirements

Util requires two webpack json stat files. More info on how to generate them.

Make sure that at least below options are set to true:

{
  // Add chunk information (setting this to `false` allows for a less verbose output)
  chunks: true,
  // Add built modules information to chunk information
  chunkModules: true,
  // Add built modules information
  modules: true,
  children: true
}

Optionally for more information use:

{
  // Add the origins of chunks and chunk merging info
  chunkOrigins: true,
}

Additional arguments

  • --chunk-name: Print only information about this specific chunk name
  • --a-name: Set name to be used for 'a' changes.
  • --b-name: Set name to be used for 'b' changes.
  • --verbose: Print more details (including module details)
  • --child-index: Show only child with given index. By default all children are processed.
  • --lose-matching: Looselly match children, instead of exact entrypoints matching. Usefull when we know that children project chunk definition changed. By default exact entrypoints matching is used.