Unknown argument: --env

Describe the bug

I'm trying to set my webpack env for configuration purposes with

webpack --env.platform=node

But, webpack-cli keeps throwing ⬢ webpack: Unknown argument: --env error to me

What is the current behavior?

webpack-cli refuses to read the flag and throw an error instead

To Reproduce
Steps to reproduce the behavior:

Just try to add --env flag to any webpack command.

Expected behavior

webpack-cli should accept and set this variable correctly

Screenshots

Additional context

This works on 3.3.10. I'm currently using 4.0.0-beta.2

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.

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

I'm seeing this issue in the 4.0.0 release

@robertlevy

Hi, @robertlevy we've changed the env flag format in v4 because we changed the arg parser, new docs will be released on official site soon. Meanwhile, you can use CLI docs from this deployment - https://vercel.com/webpack-docs/webpack-js-org/e6mjiydwu

@anshumanv

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

@robertlevy

@robertlevy ofcourse! You should get a good idea from this test - https://github.com/webpack/webpack-cli/blob/master/test/config/type/function-with-env/function-with-env.test.js

Let us know if you run into any problems 😄

@anshumanv

@anshumanv
so, env now only supports boolean values?
I need to be able to pass arbitrary strings from the command line.

@thealjey-eib

but we cannot pass an arbitrary string from the command line?

@thealjey-eib You can pass any arbitrary string from the command line.

@snitin315

@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

@thealjey-eib

@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.

@thealjey-eib

@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.

I am used to do it this way:

npx webpack --mode production --config webpack.config.build.js --env.name="[staging|production]" --env.service="[login|flight|reservation|...]"

Now I get
[webpack-cli] Unknown argument: --env.service=staging
[webpack-cli] Unknown argument: --env.name=login.

What's the working equivalent in Webpack CLI 4.x and Webpack 5.x?

When I change the syntax to your example, the properties in env are just booleans:

npx webpack --mode production --config webpack.config.build.js --env name="[staging|production]" --env service="[login|flight|reservation|...]"

# Result in env
{ 'service=staging': true, 'name=login': true }

But that's not what I need.

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 #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?

Is that something you can work with?

Yeah, of course. Thanks!

@anshumanv

@anshumanv my example is a multi-application project
I have an "applications" folder and I want to build any one of them by name.
Maybe env is not ideal, I do not know, but I have not been able to find a better way to pass custom variables into webpack.config.js
I cannot hardcode the names of every app in webpack.config.js, and even if I did a boolean value is just not suitable for getting a single value from a list.

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

@evolopment Maybe you can help fixing it :) Here's the source page https://github.com/webpack/webpack.js.org/blob/master/src/content/guides/environment-variables.md to edit.

@cranphin see #1939 for new --env format.

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.

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

@AsebWebDev

@AsebWebDev yep exactly!

Upgrades `webpack-dev-server` and `webpack-cli`

Upgrades `webpack-dev-server` and `webpack-cli` (#1229)

Please open an issue in angular-cli repo

(with versions "webpack": "^5.73.0" and "webpack-cli": "^4.10.0")

This solved the issue for me:

/package.json -->
"scripts": {
"start": "webpack --mode=development && nodemon server",
"build": "webpack --mode=production && NODE_ENV=production",
...
}

Hope it helps.

Navigation Menu

Repository navigation

Unknown argument: --env #1216

2 remaining items

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Unknown argument: --env #1216

Description

Activity

lobsterkatie commented on Feb 11, 2020

ematipico commented on Feb 12, 2020

robertlevy commented on Oct 11, 2020

anshumanv commented on Oct 11, 2020

robertlevy commented on Oct 11, 2020

anshumanv commented on Oct 11, 2020

thealjey-eib commented on Oct 12, 2020

snitin315 commented on Oct 12, 2020

thealjey-eib commented on Oct 12, 2020

anshumanv commented on Oct 12, 2020

fabianmarcus commented on Oct 12, 2020

anshumanv commented on Oct 12, 2020

fabianmarcus commented on Oct 12, 2020

thealjey-eib commented on Oct 12, 2020

2 remaining items

anshumanv commented on Oct 12, 2020

chenxsan commented on Oct 18, 2020

snitin315 commented on Oct 21, 2020

ZebraFlesh commented on Dec 15, 2020

AsebWebDev commented on Dec 22, 2020

snitin315 commented on Dec 22, 2020

alexander-akait commented on Jun 15, 2022

Carles11 commented on Jul 18, 2022

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions