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-split-by-path

v2.0.0

Published

Split a Webpack entry bundle into any number of arbitrarily defined smaller bundles

Downloads

15,002

Readme

Split By Path Webpack Plugin

This plugin will split a Webpack entry bundle into any number of arbitrarily defined smaller bundles.

Based on Split by Name Webpack Plugin.

Unlike original component, it uses absolute path to identify bundle.

Why?

  • Browsers will open [between 6 and 10][browserscope] parallel connections to a single host. By splitting up one large file (your main bundle) into a number of smaller ones, you can leverage these connections to download the files [faster][stevesouders].
  • It's likely that you will have some third party scripts which you change infrequently. By putting these into their own bundle, then if they haven't changed between builds, your users may still be able to use the cached version from before.

How?

Configuration of the plugin is simple. You instantiate the plugin with an array of objects, each containing the keys name and path. Any modules which are in your entry chunk which match the bucket's path (first matching bucket is used), are then moved to a new chunk with the given name.

path should be an absolute path string value. It can be also an array of such values.

Creating a 'catch-all' bucket is not necessary: anything which doesn't match one of the defined buckets will be left in the original chunk.

Now, by separating the manifest info into a standalone chunk, vendor chunks(something like that) will stay the same with or without hashing unless you change their version.

API

new SplitByPathPlugin(chunks, options);

  • chunks - array of objects { name: string, path: string | string[] }
  • options - object, optional { ignore: string | string[], ignoreChunks: string | string[], manifest: string }
new SplitByPathPlugin([
  { name: 'c1', path: 'src/c1' },
  { name: 'vendor', path: path.join(__dirname, 'node_modules/')},
  ...chunkN
], {
  ignore: [
    'path/to/ingore/file/or/dir1',
    'path/to/ingore/file/or/dir2'
  ]
});

Example

var SplitByPathPlugin = require('webpack-split-by-path');
module.exports = {
  entry: {
    app: 'app.js'
  },
  output: {
    path: __dirname + '/public',
    filename: "[name]-[chunkhash].js",
    chunkFilename: "[name]-[chunkhash].js"
  },
  plugins: [
    new SplitByPathPlugin([
      {
        name: 'vendor',
        path: path.join(__dirname, 'node_modules')
      }
    ], {
      manifest: 'app-entry'
    })
  ]
};

So every module that is being requested from node_modules will be placed in public/vendor.js and everything else will be placed in public/app.js.