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

webpack2-externals-plugin

v1.0.0

Published

Provides more powerful externals configuration options

Downloads

561

Readme

webpack2-externals-plugin

This is a fork of webpack-externals-plugin, but that works in Webpack 2.

Provides more powerful externals configuration options.

Usage

new ExternalsPlugin({ type, test, include, exclude }), where:

  • type represents the type of external (/var|this|commonjs2?|amd|umd/). Defaults to options.output.libraryTarget.
  • test, include, exclude work as they do with loader configuration.

Example

The following webpack configuration considers all modules under the local node_modules/ directory as externals.

webpack.config.js:

var ExternalsPlugin = require('webpack-externals-plugin');
module.exports = {
  entry: './app.js',
  output: {
    path: __dirname + '/dist',
    filename: 'bundle.js',
  },
  plugins: [
    new ExternalsPlugin({
      type: 'commonjs',
      include: __dirname + '/node_modules',
    }),
  ],
};

Differences with options.externals

Webpack externals are only filtered depending on the user request (require('webpack') => webpack).

With this plugin, externals are filtered depending on the path of the resolved module (require('webpack') => <dir_path>/node_modules/webpack/lib/webpack.js).

This lets you include or exclude entire directories depending on the actual path of the resolved module.