Support argv as second config param about parallel-webpack

[mzealey]

This is also an issue for me. Webpack passes an object containing the argv (eg {mode: 'production'}) as 2nd argument to module.exports

[pago]

I'm happy to merge a PR that adjusts this according to your needs.

[HaNdTriX]

closing for know, unit I got additional infos on the topic.

[eugef]

I also have the same issue - not able to access argv.mode when using like this:

module.exports = (env, argv) => {
}

@HaNdTriX are there any planms to fix it? As it is impossible to simply replace webpack with parallel-webpack in cli.

[HaNdTriX]

@eugef I am not the author/contributor of this package.

Nevertheless, I reopen this issue for you guys. I am not using parallel-webpack anymore.

[eugef]

Are you using smth else instead?

[HaNdTriX]

Nope.

[iorrah]

This also works:

package.json

"scripts": {
  "start": "parallel-webpack -- --foo=bar"
}

webpack.config.js

const parser = require('yargs').parse;

const parsedArgv = parser(process.argv);
console.log(parsedArgv.foo); // bar