-
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
Private npm package; unable to install in yarn 1.0.1 #4335
Comments
You may just need to reauthenticate in |
I'm seeing this issue as well against a private npm modules I have. |
I just had the same issue and managed to fix by setting the npm registry in the yarn config and recreating the yarn.lock file.
|
We're also seeing an issue that yarn no longer seems to handle reading .npmrc correctly, after installing 1.0.1.
|
Could be related to #4339? |
I'm only running into this issue when running yarn inside a docker container using Ubuntu 16. I'm not able to reproduce this issue on OSX 10.12 (with or without If I remove the Can anyone else confirm if you're having issues on Ubuntu as well? |
Same issue here, been waiting a long time to upgrade from In any scenario, if I roll back to |
Just recreating the yarn.lock file was sufficient for me, no need to change the registry config. |
@aiham I am able to recreate the yarn.lock file successfully but any following install using the lock file fail. Having to recreate the lock file every time defeats the purpose. |
@narkeeso I only had to recreate it once. |
Based on the PRs @BYK has posted, I probably fixed this for myself when I reverted my registry config to the default value: |
Same issue here. Using a private NPM registry. It couldn't find any packages with yarn 1.0.1. If I roll back to 0.28.4, everything starts working again. My private repo is configured in the .npmrc file and is using basic auth. If I do |
Okay, let's wait until these are merged and we release 1.0.2 or at least have a nightly with both fixes. Anyone up for testing if these fix the issue? |
@BYK I can, just poke me when it's available! |
@maroy1986, thanks! Here you go https://yarnpkg.com/en/docs/nightly |
@BYK No luck for me on the
I'm going to drop a comment on #3622 as well. |
Adding a trailing slash like described in #4339 works for me |
This is on Travis. The way we set up the private NPM tokens are like this: echo "//registry.npmjs.org/:_authToken=${NPM_TOKEN}" > ~/.npmrc`
echo "//registry.npmjs.org/:_authToken=\${NPM_TOKEN}" > .npmrc Has the format of this changed somehow? I upgraded local yarn to 1.0.1, then wiped the I looked at #4339, but I don't set up a |
@BYK Just tried it and the nightly build works for me! |
@maroy1986 yay! |
@ryanpatrickcook can you give the latest nightly a try to see if it fixes your issue? |
@BYK Well apparently I've talked too fast : Log :
Going back to prior 1.0.0 version make it works again... At least the error isn't the same! |
@maroy1986 this says unauthorized and the package doesn't seem to be scoped so may be you actually need |
@BYK You're right, that was it. I also found that I can now remove my basic auth line in my .npmrc and leave the token base auth only, which wasn't working before, that's good news and way more secure than having my private repo password unencrypted in my .npmrc file! Waiting for 1.0.2 release to update my builder docker image to Yarn 1.x ! 🚀 |
I can confirm that it works again with v1.0.1-20170911.1702 |
When can we expect a release? Or can I install nightly using the installation script? Oops, realized I can run |
@rolandjitsu you can install nightlies here https://yarnpkg.com/en/docs/nightly |
@kaylieEB thanks, just found that flag in the bash script. |
Yeah, a release is very soon. |
See also #4451 |
FWIW, I simply had to delete the lock file. Googling for a failure to yarn install private repos gets you here, and I suspect many people will have the same issue I just had: Steps to Repo:
Steps to fix:
|
If your package is hosted privately on npmjs.org, removing the line |
on yarn 1.3.2 and still getting this error.
in order to resolve it Update: After cleaning cache and attempting #4335 (comment)
also worked. |
@huw this work for me. I can't add private package by yarn, then I try to delete this line in my
thanks for your remind. |
I'm unable to
yarn install
when using a private npm package using yarn 1.0.1 when working in previous versions.yarn install returned exit code 1
Action failed: yarn install
auth token in .npmrc file
Ubuntu 14.04.4 LTS
node: v4.2.6
yarn: 1.0.1
Mac 10.11.6
node: v6.9.4
yarn: 1.0.1
yarn-error.txt
The text was updated successfully, but these errors were encountered: