-
-
Notifications
You must be signed in to change notification settings - Fork 622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] chore: migrate to commander #1347
Conversation
@rishabh3112 The tests look fine, but there are code style issue in your Pull Request. Please review the following:
See complete report here. |
How's the progress on this? @rishabh3112 |
@anshumanv @rishabh3112 need help, I want to look at that on the next week, but feel free to go ahead |
I couldn't resolve the 3 tests which are failing. Need help in that. |
I guess #1455 should fix |
Closing in favour of #1481 |
Refers #717
What kind of change does this PR introduce?
Migration to new arguments parser
Did you add tests for your changes?
No, needs verification
If relevant, did you update the documentation?
No, ideally shouldn't be needed
Summary
Use commander as decided at #717 (comment)
Does this PR introduce a breaking change?
Don't mean to, attempting as seamless transition as possible
Other information
Tasks needed to be done.
Handle custom typeswebpack-cli/packages/webpack-cli/lib/utils/cli-flags.js
Line 284 in 6eecb26
commander.js
webpack serve help
command-line-args
completelyProcess global flag correctly( cli-team decided to drop support for it.)