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

entry-generator-webpack-plugin

v1.0.0

Published

A Webpack plugin to dynamically generate an entry file on compiler initialisation

Downloads

19

Readme

Entry Generator Webpack Plugin

NPM

A Webpack plugin to dynamically generate an entry file on compiler initialisation

Rationale

Sometimes you will want to generate an entry file dynamically. This file may consist of your bower dependencies or it may be a test suite that consists of all your unit test specification files.

This plugin will generate such a file if it is not already present. You may depende your compiler upon the output of this plugin.

Usage

The plugin is of the following form.

new EntryGeneratorWebpackPlugin(outputFile, sources)

where:

  • outputFile is the javascript file that will be generated
  • sources is a function|Array.<function> of methods that return a list of files or promise to such

Webpack configuration

The following configuration generates a vendor.js files that consists of your bower dependencies.

var EntryGeneratorWebpackPlugin = require('entry-generator-webpack-plugin')

module.exports = {
	entry; {
		vendor: 'vendor.js'
		...
	},
	...
	plugins: [
		new EntryGeneratorWebpackPlugin('vendor.js', [
			EntryGeneratorWebpackPlugin.bowerDependenciesSource(),
			...
		]),
		...
	]
}

The sources are one or more function([outputPath:string]):Array.<string>|Promise. It returns a list of files relative to the given output path or a list of module names or a promise that resolves to such.

Sources

There are a number of source factories exported on EntryGeneratorWebpackPlugin, these include:

  • EntryGeneratorWebpackPlugin.bowerDependenciesSource([options])

    A source factory that will list bower modules from the dependencies field of the bower.json file in the Webpack context directory. The options may include any of the standard Webpack file filters (although applied to the module names), meaning test, include, exclude.

  • EntryGeneratorWebpackPlugin.bowerDevDependenciesSource([options])

    As above, for the devDependencies field.

  • EntryGeneratorWebpackPlugin.globSource(pattern, [options])

    A source factory that can glob files rooted in the Webpack context directory. It supports options per glob properties. The options may also include any of the standard Webpack file filters (although applied to the module names), meaning test, include, exclude. Note however that it is more efficient to use the glob ignore property than the Webpack exclude regular expression.