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 🙏

© 2026 – Pkg Stats / Ryan Hefner

webpack-import-splitter-loader

v1.0.4

Published

Let's say that our project has a `util.js` file with several functions in it and a dynamicallly loaded module that calls some of those functions:

Readme

Overview

Let's say that our project has a util.js file with several functions in it and a dynamicallly loaded module that calls some of those functions:

util.js

export function getRandomInt() {...}
export function getSanitizedFilename() {...}
export function mapAndFilter() {...}

index.js

import { getRandomInt } from './util.js';

const dynamicallyImportedModule = import('./dynamic-module.js');

dynamic-module.js

import { getSanitiedFilename, mapAndFilter} from './util.js';

After compiling, we end up with two chunks, dist/main.js and dist/dynamic-module.js. We might expect that the code of getSanitizedFilename() and mapAndFilter() would end up in dist/dynamic-module.js and getRandomInt() in dist/main.js, but instead, the code of every function in util.js is placed into dist/main.js.

This loader makes it so that the code is split like we might have expected, with getSanitizedFilename() and mapAndFilter() being placed into dist/dynamic-module.js and getRandomInt() into dist/main.js. This can decrease the size of your main bundle, especially if you have a lot of functions that are called by your dynamically loaded module and are not called elsewhere.

Setup

Installation

Install webpack-import-splitter-loader as a dev dependency (yarn add webpack-import-splitter-loader -D or npm install webpack-import-splitter-loader -D)

Add loader to webpack.config.js

For performance sake, I'd recommend only enabling the loader for production builds.

module: {
  rules: [
    {
      test: /\.(js|jsx|mjs)$/,
      use: [
        process.env.NODE_ENV === 'production' &&
        {
          loader: 'webpack-import-splitter-loader'
        }
        // ...(other loaders)
      ]
    }
  ]
  // ...
}

Add VirtualUrlPlugin to webpack.config.js

webpack-import-splitter-loader relies on Webpack.experiments.schemes.VirtualUrlPlugin, and I haven't yet figured out how to have the loader dynamically add it, so for now, you also need to add this configuration to webpack.config.js:

plugins: [
  new Webpack.experiments.schemes.VirtualUrlPlugin(
    {
      '__unused__': ''
    },
    'webpack-import-splitter-loader'
  )
// ...
]

Limitations

  • Non-ESM modules are skipped.
  • When using Yarn Berry, the loader will generally not process sub-dependencies.