You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to run webpack-cli serve with the logging flag set to info like this: webpack-cli serve --client-logging info. It seems that the info string was identified, and instead of running webpack-cli serve it just outputted system information like it would with webpack-cli info. Since info is a valid option for logging, we need to do more than just check that there is an info string in the argv.
To Reproduce
Put info as an option for something in a way that is valid, and the CLI will end up running webpack-cli info.
Expected behavior
webpack-cli info should not be run in certain cases
The text was updated successfully, but these errors were encountered:
This seems to be happening because info comes before serve in cli-flag definition. webpack serve --client-log-level info
The present way of parsing commands picks info over serve.
Describe the bug
I was trying to run
webpack-cli serve
with the logging flag set toinfo
like this:webpack-cli serve --client-logging info
. It seems that theinfo
string was identified, and instead of runningwebpack-cli serve
it just outputted system information like it would withwebpack-cli info
. Sinceinfo
is a valid option for logging, we need to do more than just check that there is aninfo
string in the argv.To Reproduce
Put
info
as an option for something in a way that is valid, and the CLI will end up runningwebpack-cli info
.Expected behavior
webpack-cli info
should not be run in certain casesThe text was updated successfully, but these errors were encountered: