Add support for webpack.config.*.js

[astynax777]

With VS 2017 there is an Angular template that include webpack and both a webpack.config.js and a webpack.config.vendor.js. Currently, I cannot use the webpack task runner extension to execute the webpack.config.vendor.js because it doesn't match one of the filenames. The convention appears to be to name your config files webpack.config.

.js. The new Angular template vs project builds this by adding the following line to csproj: <Exec Command="node node_modules/webpack/bin/webpack.js --config webpack.config.vendor.js" /> Could we add support for any files that start with webpack.config.*?

[nathonius]

I'm in the same boat.

We use a base webpack.config.js that cannot be run alone. It is the common config, while we have webpack.config.dev.js and webpack.config.prod.js which load the common config and fill in / overwrite what's left.