Open STRML opened 8 years ago
Was able to reproduce this locally with our private registry.
I can confirm the issue appears to be prioritizing root-level .npmrc
over even local .yarnrc
files. My root .npmrc
is not configured to our private registry (I use a command alias for instead). Moving it over fixes the issue.
I can also confirm the same problem. .yarnrc seem to be ignored, when I created .npmrc with same settings, yarn started to pull packages from our local repository. Looks like the support for .yarnrc has been dropped
Is that documented anywhere?
We have a local registry specified in our
.yarnrc
.This particular error manifests with a fork we're temporarily using of
ampersand-collection-lodash-mixin
. We typically use very high version numbers for this. The returned package manifest contains the versions0.50.0
and0.51.0
, as well as the base package's versions(1.0.1-4.0.0)
.With 0.15.1,
outdated
worked fine:But in 0.16.1, we have the following error:
I read #1073 which seemed to have some success with
yarn set config
and/or some trailing slashes, but none of this worked for us.Looking at our server logs, I am not seeing any actual hit for the package metadata. Clearing cache does not help.