You can easily do this by your own, as the webpack.config.js is just a node.js module and allows to execute any code.

var glob = require("glob");
// ...
entry: glob.sync("./test/**/*Spec.js")

@sokra could this be reopened? If wildcards are supported out of the box more people will know how to use them, and the watch functionality can detect new files...

+1 for wildcard support.

wildcard support would allow config file to be json, or put into package.json

@sokra there's another use case for wildcard entry points: not needing to restart webpack -watch when a new file is added. We have a lot of entry points for various reasons (eg: being able to run unit tests on a smaller subset of the files during development), and whenever someone adds a new test file, they'd have to restart webpack for it to get picked up, while everything else is handled by -watch.

+1

+1

@sokra this is mostly for the CLI not the config file, as you said the config file is fine and using glob.sync just works.

+1

+1

+1

A possible workaround is to use require.context:

// webpack.config.js
entry: "test/all.js"

// test/all.js
var req = require.context('./', true, /Spec\.js$/);
req.keys().forEach(req);

Thanks @cspotcode. 👍 🌟