webpack-cli: Unknown argument: --env

@snitin315 how?

it used to be as simple as webpack --env.app=foobar --env.title=qwerty but, now this throws “Unknown argument” errors

this creates variables with names app=foobar and title=qwerty, and values true webpack --env app=foobar --env title=qwerty

Thanks for the examples, migration of both config and scripts to use booleans will add a considerable overhead and current format seems not the most verbose thing to work with. I’ve opened https://github.com/webpack/webpack-cli/issues/1932 to track it, will PR soon

Since we’ve migrated our arg parser to commander so --env.name="staging" --env.service="login" won’t be possible but we can do --env name=staging --env service=login Is that something you can work with?

This is a breaking change that really needs to be called out as such. In addition, I don’t think webpack-cli 4.x can claim compatibility with webpack v4 with this change – the --env.prod=foo form is explicitly called out in the webpack v4 docs. If there is no desire to undo this change, then the peerDependencies should change.

I am having the exact same problem with the mode flag. And yet the docs still include it, and the migration guide for webpack 4 -> 5 mentions it, so it’s pretty clear it hasn’t been removed… Very confused with this one.

So, setting up the enviroment variables like this is the way to go: --env prod=foo - no dot notation.

Can there be some easy to find simple fix for this? A lot of people are going to be running into this now, I read the comments and I’m still not sure what the exact fix is

PR sent. Thanks.

I don’t want a config per application either, because they would all be the same. It would only complicate things.

Please don’t install 4.0.0-beta.2 just yet. Unfortunately I published an incorrect version on npm, so sorry about that. Please keep using 3.3.10 or 3.3.11.

In 4.0.0-beta.2 we removed --mode and --env. If you feel you’d need that argument back, feel free to leave a feedback here

Ah okay so you have a single config for all applications, then env is the way to go 👍

@thealjey-eib for now yes, this is how the behaviour was restored when it was removed.

You can use

webpack --env appFoobar --env titleQwerty

And use these variables to write conditional logic in your config, does it not cover your use case? If not, please give an example.

@anshumanv thanks but that link is not working for me. could you paste a summary or working example?

I’m seeing this issue in the 4.0.0 release