@wildpeaks/glob-webpack-plugin

Glob Webpack Plugin

Webpack 4.x plugin to define entry using a glob.

It also updates the list of entries in --watch mode, without having to restart Webpack.

---

Quickstart

Install:

npm install @wildpeaks/glob-webpack-plugin

Then use it in your webpack.config.js:

const GlobPlugin = require('@wildpeaks/glob-webpack-plugin');

module.exports = {
	target: 'web',
	plugins: [
		new GlobPlugin({
			entries: './src/*.js'
		})
	]
};

---

Entry identifiers

By default, it uses the filename as Entry Name.

So, for example, ./src/app1.js would produce this entry:

{
  "app1": "./src/app1.js"
}

You can provide a function to provide a custom name:

const {basename} = require('path');
const GlobPlugin = require('@wildpeaks/glob-webpack-plugin');

module.exports = {
	target: 'web',
	plugins: [
		new GlobPlugin({
			entries: './src/*.js',
			entriesMap: filepath => 'bundle-' + basename(filepath, '.js')
		})
	]
};

In this example, ./src/app1.js would produce this entry:

{
  "bundle-app1": "./src/app1.js"
}

---

Polyfills

Property polyfills prepends modules to every entry:

const {basename} = require('path');
const GlobPlugin = require('@wildpeaks/glob-webpack-plugin');

module.exports = {
	target: 'web',
	plugins: [
		new GlobPlugin({
			entries: './src/*.js',
			polyfills: [
				'polyfill-module',
				'./src/local-polyfill.js',
				'./src/reset.css'
			]
		})
	]
};

---

Known limitations

It currently overwrites entry (because it's meant to replace), so if you need multiple globs, your webpack.config.js can export an array of Webpack configs, each with its own glob.

On Windows, merely renaming or deleting an entry doesn't trigger a rebuild, but creating or updating files do.