-
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
Scoped Packages - "yarn add" (not "yarn") throws error #5263
Comments
Seems to work OK for me.
Maybe try upgrading to yarn v1.4 and see if it's already fixed? |
No, I still see the issue on windows 7.
|
Still an issue on win10 with yarn 1.6.0
|
I still can't reproduce this. Tried on Win 10, yarn 1.5.1, powershell and it still worked for me. If someone why can consistently reproduce this can help debug, we would appreciate it. What should happen is that yarn uses the url |
I was playing around and found out it doesn't happen in windows terminal, but it fails when attempting |
macOS 10.13.2 Problem persists after upgrading to node 9.11.1 and yarn 1.6.0. Same if I add the package to my
|
Can confirm this issue |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
Yarn add command cannot install this published package: https://www.npmjs.com/package/@google-cloud/translate
npm can install it correctly:
"yarn" does install it correctly if it is in the package.json, it is just "yarn add" that fails.
Interestingly, bluebird gives a slightly different error:
Both work from package.json, and wrapping them in quotes in yarn add doesn't matter.
Please mention your node.js, yarn and operating system version.
yarn 1.3.2
node v8.9.4
Windows 7
Related: #4354 #4366
The text was updated successfully, but these errors were encountered: