Yarn 1.10.1 does not work when your build environment are used with both a local repository and the npm public registry, however Yarn 1.9.4 does

[mgentile6]

With a new build environment I installed yarn 1.10.1. Our environment uses a local Nexus repository "yarn-private" and during build time also downloads open source packages from https://registry.yarnpkg.com/. I ran the "yarn config set registry ..." to reference our local Nexus repository it also created the new .yarnrc file in users home directory. When I ran "yarn install" I would get the error below:

yarn install v1.10.1
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/4] Resolving packages...
error Couldn't find package xxxxxx required by xxxxxxx on the "npm" registry.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I then did a "npm uninstall -g yarn" followed by "npm install -g yarn@1.9.4" and the build worked. And I changed nothing else. Something must have changed in between yarn versions 1.9.4 and 1.10.1.

[eaustin]

I have the same issue and the performance is pretty bad. Takes a long time to even get to the error.

[nertzy]

This issue is pretty stale at the moment. Is this still a problem or can this be closed?