-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Cannot add "progress" module #2220
Comments
Same problem here. My environment:
Thanks for the workaround @KenanSulayman. 👍 |
The issue is in src/cli/index.js, when commander parses args and progress becomes the first argument besides startArgs (node yarn), it is parsed as an option since --no-progress option is defined above. A quick fix would be to add commandName back when parsing args, but that looks like a workaround: https://gist.github.com/iredchuk/689e7cf949e22c708b68befb7662855d |
Didn't work with commander before, but this behaviour looks weird to me: the last case is what's happening here when the arg is lost due to the name collision with an option: https://gist.github.com/iredchuk/ab253c68a880d45e0ab99d853fc56ddc Wonder if it's possible to change this via some commander settings, e.g. do not parse arg as option when it's not preceded with '--'? |
workaround: |
Duplicate of #2112 |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Works for all other modules; a workaround is
npm i --save progress
and thenyarn
.What is the expected behavior?
install and add the module
Environment
yarn v0.17.10
node 7.2.1
OS information is classified, sorry.
The text was updated successfully, but these errors were encountered: