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

chunk-webpack-plugin

v0.1.10

Published

Moves select modules into target chunk

Downloads

8

Readme

chunk webpack plugin

What does it do?

This plugin transfers modules whose absolute path matches a regular expression from a list of chunks into a single target chunk. Coupled with other plugins – especially with webpack's built-in CommonsChunkPlugin – this can be quite useful.

Usage

Example webpack config:

const webpack = require('webpack');
const ChunkPlugin = require('chunk-webpack-plugin');

module.exports = {
    entry: {
        bundle: './src/main.js',
    },
    output: {
        path: './dist/',
        filename: 'bundle.js'
    },
    plugins: [
        new ChunkPlugin({
            from: 'bundle', // or an array of strings
            to: 'vendor',
            test: /node_modules/ // or an array of regex
        }),
        new webpack.optimize.CommonsChunkPlugin('vendor', 'vendor.js'),
    ]
};

With this configuration all the modules that were require'd in the bundle chunk whose absolute path contains the substring "node_modules" would be instead added to the vendor chunk – and not into the bundle chunk where they would otherwise be.

But why?

Using this on external bundles can greatly increase re-build performance for the bundle chunk, especially if it includes a lot of modules that you have no intention of changing.

Note

The issue with using only the CommonsChunkPlugin plugin to achieve this behavior is that it requires that you keep an explicit list of modules that you want to be transferred into the the target bundle.
This plugin tries to solve that problem by matching module paths against regular expressions and transferring the matched modules to the target chunk (in the case of the configuration about it's the vendor chunk) before the CommonsChunkPlugin has a chance to run, but still letting it do its magic.

License

ISC