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 🙏

© 2025 – Pkg Stats / Ryan Hefner

multidefine-library-webpack-plugin

v0.3.2

Published

This plugin allow webpack 2 to bundle your code to a named amd library with multiple entries in a same asset.

Readme

Multidefine Library Webpack Plugin

This hack plugin allow webpack 2 to bundle your code to a named amd library with multiple entries in a same asset.

Requirements

  • node >= 6.9.4
  • webpack >= 2.2.0

Installation

npm install multidefine-library-webpack-plugin --save

Or add it to your package.json

Usage

Phase 1: config

Add the plugin in your webpack.config.js:

'use strict';

const MultidefineLibraryWebpackPlugin = require('multidefine-library-webpack-plugin');

module.exports = {
  entry: ['a.js', 'b.js'],
  output: {
    path: './build',
    filename: '[name].js'
  },
  plugins: [
    new MultidefineLibraryWebpackPlugin([{
      path: 'a.js',
      name: 'A'
    }, {
      path: 'b.js',
      name: 'B'
    }])
  ]
};

###Phase 2:

???

###Phase 3: profit

Now, you can requirejs your modules:

require(['A', 'B'], function (A, B) {
  // A and B are available !
});

This plugin support amd, umd and commonjs source module.

Configuration

First parameter: modules to expose

The plugin take an array of objects as first parameter. Each object will represent an entry point of your asset:

[{
  path: "a.js", // path to the file that you want to make requireable
  name: "A", // Define name of the module
  [aliases: ["alias1", "alias2"]] // alternate deprecated names exposed for this module
  [deprecated: true/false] // If deprecated, a global method "deprecated" is called is this module is used
}]

This plugin can also take an object as parameter. Each key will represent an entry point of your asset:

{
  "a.js": { // path to the file that you want to make requireable
    name: "A", // Define name of the module
    [aliases: ["alias1", "alias2"]] // alternate deprecated names exposed for this module
    [deprecated: true/false] // If deprecated, a global method "deprecated" is called is this module is used
  }
}

Second parameter: options

The plugin take an options object as second parameter.

    new MultidefineLibraryWebpackPlugin(modulesToExpose, {
      deprecationMethodName: 'deprecated' // global method name to call to notify deprecated usage
    })