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

@emmiep/rollup-plugin-split-bundle

v1.0.0

Published

An experimental bundle splitter plugin for Rollup

Downloads

3

Readme

@emmiep/rollup-plugin-split-bundle

Experimental Rollup plugin to split the code into separate bundles, for instance to create a "vendor bundle" with external npm packages. This is not code splitting for asynchronous loading with dynamic imports, such as using webpack and and import(). Use on your own risk, not tested and not recommended for production code!

Usage

Installation:

npm install @emmiep/rollup-plugin-split-bundle

The plugin requires two rollup configurations, one for the main bundle (the "consumer" side) and one for the split bundle (the "producer" side).

First, use the consumer() plugin in the main bundle configuration (rollup.main.js):

import splitBundle from '@emmiep/rollup-plugin-split-bundle';

export default {
  input: 'src/index.js'
  output: {
    file: 'dist/app.js'
    format: 'umd',
    name: 'app'
  },
  plugins: [
    splitBundle.consumer({
      name: '__vendor',
      modules: [
        'react',
        'react-dom'
      ]
    })
  ]
};

Then, use producerFromConfig() in the split bundle configuration (rollup.vendor.js) with the main bundle configuration:

import splitBundle from '@emmiep/rollup-plugin-split-bundle';
import mainConfig from './rollup.main';

export default {
  output: {
    file: 'dist/vendor.js'
    format: 'umd',
    name: 'vendor'
  },
  plugins: [
    splitBundle.producerFromConfig(mainConfig)
  ]
};

Then invoke rollup with both configuration files:

rollup -c rollup.main.js
rollup -c rollup.vendor.js

Background

The idea behind the plugin is straightforward and can easily be done manually as well.

The consumer prevents the listed modules from being included in bundle by declaring them as external, and map their module IDs to properties on a global variable (e.g. window.__vendor) using output.globals. The name of the global variable is set by the name plugin option.

On the other hand, the producer simply sets output.name to the same name as the global variable, and replaces the entrypoint with a script re-exporting the modules so the main bundle can access them:

export {default as React} from 'react';
export {default as ReactDom} from 'react-dom';