v4-beta : use env variable with config as a function

Describe the bug

We need to manipulate env vars in the config file to adjust the compilation entries points

What is the current behavior? Cli does not recognize --env.MYVAR parameter Config returning this kind of result is not considered by CLI without any error message : module.exports = (env) => { return { // my conf }

To Reproduce

encapsulate your config object in a function and try to compile it.

Expected behavior

CLI should receive config functions and --env parameters

Screenshots

Compilation results without function

Compilation result with function

Unknown --env params

[snitin315]

Agreed.

[alexander-akait]

For complex cases you should use webpack.config.js, no need to support misleading behavior weback-cli --resolve-alias-alias alias1 alias2 can be weback-cli --resolve-alias-alias index.js main.js and you can never understand what the developer meant