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

auto-require-webpack-plugin

v1.0.1

Published

Webpack plugin to automatically require the module itself

Downloads

10

Readme

auto-require-webpack-plugin

Webpack plugin to automatically require the module itself, if module name defined. For Example:

(function webpackUniversalModuleDefinition(root, factory) {
	if(typeof exports === 'object' && typeof module === 'object')
		module.exports = factory();
	else if(typeof define === 'function' && define.amd)
		define("common/view", [], factory);
	else if(typeof exports === 'object')
		exports["common/view"] = factory();
	else
		root["common/view"] = factory();
})(this, function() {
  /* Module code here */
});

// When using require, call the module automatically
typeof define === 'function' && define.amd && require(['common/view']);

Usage

new AutoRequirePlugin(options)

/* Use constructor options directly */
var options = true;

module.exports = {
  plugins: [
    new AutoRequirePlugin(options)
  ]
};

Or

/* Use `output.autoRequire` to set options */
var options = true;

module.exports = {
  output: {
    autoRequire: options
  },
  plugins: [
    new AutoRequirePlugin()
  ]
};

There are two ways to configure AutoRequirePlugin: constructor's parameter or output.autoRequire. The latter will override constructor's parameter.

Examples

Type of options can be boolean, string, RegExp, function and Array.

Require all modules

module.exports = {
  plugins: [
    new AutoRequirePlugin(true)
  ]
};

Require module with specific name

module.exports = {
  plugins: [
    new AutoRequirePlugin('common/view')
  ]
};

Require module(s) matching regular expression

module.exports = {
  plugins: [
    new AutoRequirePlugin(/^common/)
  ]
};

Require module(s) testing by function

module.exports = {
  plugins: [
    new AutoRequirePlugin(function (moduleName) {
      return moduleName.split('/').length > 2;
    })
  ]
};

More complex case

module.exports = {
  plugins: [
    new AutoRequirePlugin([
      /^pages\/.+/,
      function (moduleName) {
        return moduleName.indexOf('common') >= 0 && moduleName.indexOf('widgets') < 0;
      }
    ])
  ]
};