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

dedupe-dependent-chunks-webpack-plugin

v1.2.0

Published

Webpack plugin to dedupe modules from chunks known to load only after others with those modules.

Downloads

6

Readme

dedupe-dependent-chunks-webpack-plugin

Webpack plugin to dedupe modules from chunks known to load only after others with those modules.

npm add -D dedupe-dependent-chunks-webpack-plugin (copy)

Suppose you have a part of your app whose code you lazy load with Webpack dynamic imports, or even react-loadable.

That lazy-loaded page may itself may lazy load other code, e.g., code below the fold or only needed on interactions. This code might only be used on this page and nowhere else in the app.

Even if the lazy-loaded page chunk and its additional lazy-loaded chunks share some common modules, Webpack may not understand that your UI guarantees that the latter will only ever be loaded after the former.

The DedupeDependentChunksWebpackPlugin lets you manually inform Webpack that it can remove shared modules from any other lazy-loaded chunks that your lazy-loaded chunks might load.

If you specify only dependent chunks, we'll automagically determine all the dependee chunks that import it, and only remove modules from the dependent that are common to all dependees.

Example webpack.config.js:

const DedupeDependentChunksPlugin = require("dedupe-dependent-chunks-webpack-plugin");

module.exports = {
  entry: "./src/index.js",
  plugins: [new DedupeDependentChunksPlugin("lazy-2-1")],
  optimization: {
    splitChunks: {
      chunks: "all",
      name: true
    }
  }
};

Or, with multiple dependees:

new DedupeDependentChunksPlugin(
  ["a-lazy-component", "another-lazy-component"] // dependees
);

Or, with explicit object of dependee-dependents mapping:

new DedupeDependentChunksPlugin({
  "some-lazy-part": "a-lazy-component-of-its" // dependee: dependent
  // etc.
});

Or, with array of dependents:

new DedupeDependentChunksPlugin({
  "some-lazy-part": ["a-lazy-component-of-its"] // dependee: dependents
  // etc.
});

Or, as array of pairs:

new DedupeDependentChunksPlugin([
  ["some-lazy-part", "a-lazy-component-of-its"] // dependee, dependent
  // etc.
]);

Or, if you need to support multiple dependee chunks for a set of dependent chunks, as array of pairs of arrays:

new DedupeDependentChunksPlugin([
  [
    ["some-lazy-part", "another-lazy-part"], // dependees
    ["a-lazy-component-of-theirs", "another-lazy-component-of-theirs"] // dependents
  ]
  // etc.
]);

See example for an (admittedly trivial) example app.

With this plugin configured for the lazy-2 chunk and dependent lazy-2-1 chunk, their shared dep-1 module dependency is not included in lazy-2-1 chunk:

Before:

(images from the webpack-bundle-analyzer)


Licensed by the MIT License.