Support for --config-name to build one or more specific configuration(s)
koen-dev opened this issue · 0 comments
Explain the problem
Let me start by pointing out that this package has improved the build time by a lot. We have about 20+ configurations that without parallel-webpack
takes about 162 seconds and with takes 82 seconds.
I just don't understand how I can only run a specific configuration like I am used to with webpack
by using the flag --config-name=<name>
.
Expected Behaviour
Ability to run a single configuration by using the flag parallel-webpack -- --config-name=<name>
or multiple by providing more than one flag parallel-webpack -- --config-name=<name> --config-name=<name>
Actual Behaviour
Runs all 20+ configuration.
Provide your webpack config
I can't share my entire webpack.config.js
but I build my config using:
module.exports = (env, argv) => { }
It returns a config array based on globs.
Let me know if more information is needed.
Provide your Environment details
-
Node version: v14.15.0
-
Operating System: Windows 10
-
webpack version: 4.44.2
-
parallel-webpack version: 2.6.0