CLI: while importing some flags have pre-appended values
See original GitHub issueBug report
While importing flags from core some flags are preappended with values , for example -
--module-no-parse
--module-no-parse-reset
--optimization-no-emit-on-errors
What is the current behavior? These flags have pre appended values and seems we cant override .
If the current behavior is a bug, please provide the steps to reproduce. Import flags and process them.
What is the expected behavior?
The flags should not have pre appended values.
Other relevant information:
webpack version:
Node.js version:
Operating System:
Additional tools:
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
list-imports — AWS CLI 1.27.34 Command Reference
Lists all stacks that are importing an exported output value. To modify or remove an exported output value, first use this action to...
Read more >Flags · CLI11 Tutorial
Adding a flag in CLI11 is done in one of three ways. ... names to default particular options to a false value or...
Read more >How to discard flags defined in imported third party packages ...
In above code sample, log package has many flags. After compiling when I execute following command, all flags including "my_flag" and flags from ......
Read more >Command Flags · oclif: The Open CLI Framework
Flag options are non-positional arguments passed to the command. Flags can either be option flags which take an argument, or boolean flags which...
Read more >Command: import | Terraform - HashiCorp Developer
-var 'foo=bar' - Set a variable in the Terraform configuration. This flag can be set multiple times. Variable values are interpreted as literal...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I have sent a fix to
commander.js
, now we wait to merge and release.I think I found the bug, I can see
defaultValue: true
inparserInstance
. Looking more into it.