-
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
add: Cannot add any module that is also an option. #1609
Comments
flat
.This actually does not replicate yarnpkg#1609, but it does show that the problem is in the CLI script itself and not the add functionality.
This actually does not replicate yarnpkg#1609, but it does show that the problem is in the CLI script itself and not the add functionality.
Looks like it's related to these two commander bugs: |
This actually does not replicate yarnpkg#1609, but it does show that the problem is in the CLI script itself and not the add functionality.
This actually does not replicate yarnpkg#1609, but it does show that the problem is in the CLI script itself and not the add functionality.
This might sound obvious but if you are facing this issue, make sure you are not accidentally running
|
Wait what parameters to pass? |
Regarding: #1609 (comment) FYI: tj/commander.js#483 has been fixed by tj/commander.js#494 |
Would you please elaborate? I created a project with |
Closing as fixed in v2. |
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Running
yarn add flat
results in:Running
yarn add flat assert
results in:Same thing happens for any package that shares a name with an option flag.
A current workaround is running
yarn add -- flat
.If the current behavior is a bug, please provide the steps to reproduce.
Run
yarn add flat
in any project.What is the expected behavior?
Yarn should install the module flat and update
package.json
andyarn.lock
.Please mention your node.js, yarn and operating system version.
node.js:
v6.9.1
andv7.0.0
yarn:
v0.16.1
OS: Ubuntu
v14.04.4
subsystem on Windows 10 ProThe text was updated successfully, but these errors were encountered: