How do I use multiple npm registries in Yarn?

javascript npm yarnpkg
kraklin picture kraklin · Nov 28, 2016 · Viewed 14.2k times · Source

I'm trying to setup Yarn 0.17.9 in our environment but I have a problem with our registry. We are currently using two registries, official npmjs and our own registry on internal network (Sinopia).

The problem is that we are using internal tool to pull packages from one or the other with --registry flag via npm install. yarn add doesn't have --registry option and I'm unable to set the custom registry globally with fallback to npmjs. I tried .npmrc but it sets only one registry for npm/yarn in project. .yarnrc doesn't seem to work and is silenced by .npmrc

Is there any way to specify two registries (fallback to second registry if the package is not found in the first one)? Or specify different npm registry per package?

Answer

Andrés Andrade picture Andrés Andrade · Nov 28, 2016

Yarn doesn't have support --registry flag as npm but you can set up your registry in .yarnrc

If your .yarnrc is being ignored it can be copied out of the ~/.yarnrc using: 

yarn config set registry http://registry.com/registry//

Related questions

How to clear cache in Yarn?

I am doing some benchmark tests for Facebook's Yarn. For this, I need to clear my global Yarn cache. Is there a command available for this? I have force-removed my ~/.yarn-cache folder, but this seems to be quite manual.

Read More
Yarn global command not working

I'm working with Yarn v0.16.1. If I understand correctly (according to the documentation), yarn global add <package> should be the equivalent of npm install -g <package>. However, when I run the example in the docs (with …

Read More
Node engine 8.x or 10.x in package.json

I tried to specify the node engine in a package.json to accept both 8 and 10 version. I tried to type this: "engines": { "node": "8.x|10.x" }, But running yarn results in: The engine "node" is incompatible with this module. Expected version "8.…

Read More