Private npm package; unable to install in yarn 1.0.1

[ryanpatrickcook]

I'm unable to yarn install when using a private npm package using yarn 1.0.1 when working in previous versions.

yarn install v1.0.1
[1/5] Validating package.json...
[2/5] Resolving packages...
⠁ [3/5] Fetching packages...
error An unexpected error occurred: “...: Request failed \“404 Not Found\“”.
info If you think this is a bug, please open a bug report with the information provided in “yarn-error.log”.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

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

[BYK]

You may just need to reauthenticate in npm or your registry. Can you try that?

[kevinold]

I'm seeing this issue as well against a private npm modules I have.

[dehbmarques]

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.

$ yarn config set registry https://registry.npmjs.org
$ rm yarn.lock
$ yarn

[evert]

We're also seeing an issue that yarn no longer seems to handle reading .npmrc correctly, after installing 1.0.1.

npm whoami correctly reports evrt, but installing private packages with 1.0.1 show a 404 Not Found error. Yesterday's yarn did not have this issue.

[ohana54]

Could be related to #4339?

[narkeeso]

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 yarn.lock).

If I remove the yarn.lock file when building my docker image, I'm able to successfully resolve private packages. That probably explains why @dehbmarques solution works, setting the registry is not actually the workaround, however removing the yarn.lock is the temporary workaround.

Can anyone else confirm if you're having issues on Ubuntu as well?

[shousper]

Same issue here, been waiting a long time to upgrade from 0.24.x, but the same issue remains.
Regardless of registry setting for npmjs.org or yarnpkg.com the problem is the same.
I have tried swapping the registry domain in our yarn.lock file, toggling my registry setting back and forth, as well as clearing my local yarn cache before each attempt.
The only way we can proceed forward with versions > 0.24.x is to delete the yarn.lock file and re-run yarn, thus forcing upgrades to all dependencies. (which is seeming like the only solution at this point 😞 )

In any scenario, if I roll back to 0.24.x and run yarn install, no matter what, it works flawlessly.

[aiham]

Just recreating the yarn.lock file was sufficient for me, no need to change the registry config.

[narkeeso]

@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.

[BYK]

This should be resolved by #4350 and/or #4347 IMO. Can anyone confirm?

[aiham]

@narkeeso I only had to recreate it once.

[aiham]

Based on the PRs @BYK has posted, I probably fixed this for myself when I reverted my registry config to the default value: yarn config delete registry

[maroy1986]

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 yarn config list I see it picks it up but doesn't seem to care about it.

[BYK]

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?

[maroy1986]

@BYK I can, just poke me when it's available!