Yarn do not respect registry defined in .npmrc file when workspaces feature is being used

[pablobirukov]

Do you want to request a feature or report a bug?
Bug

I have several packages under packages/ directory and have turned on workspaces feature.

What is the current behavior?
After I add "workspaces": [ section to package.json yarn fails with Couldn't find package "X" on the "npm" registry even though I have .npmrc on the root level and in each package with custom registry in it, lock files are here and all of them resolve package X to custom artifactory's URL.

What is the expected behavior?

yarn does not fail and resolves packages from the registry defined in .npmrc

Please mention your node.js, yarn and operating system version.
macOS 10.12.6
node v7.10.0
yarn 1.0.2

[thedevelopnik]

We're having the same issue, more than a year later.

[mohanraj-r]

This is annoying and unexpected. Some workarounds are documented in https://doppelmutzi.github.io/yarn-workspaces-bug/

[flyon]

bump. This is quite cumbersome with workspaces that have 30 modules. Copying updates to the npmrc file to each module ... should be a simple fix?

[af-mikecrowe]

As a workaround, you can update your .yarnrc by running

yarn config set "registry" "https://....."

to define your private registries. Best I can determine, only the actual registry key is defaulted to https://registry.yarnpkg.com -- all other .npmrc fields are included

[paul-soporan]

Closing as in v2 (where you need to use a .yarnrc.yml file instead) this won't be a problem.

https://yarnpkg.com/getting-started/migration