Is there any way to configure multiple registries in a single npmrc file

Question

Here is my problem  We have a private NPM registry which only works in VPN  I would like to have a fallback registry https   registry npmjs org so that when I am out of VPN it works seamlessly   P S  Currently I am using npmrc which does a good job in switching between  npmrc files as a workaround

User · Answer

You can have multiple registries for scoped packages in your .npmrc file. For example:

@polymer:registry=<url register A>
registry=http://localhost:4873/

Packages under @polymer scope will be received from https://registry.npmjs.org, but the rest will be received from your local NPM.

User · Answer

Not the best way but If you are using mac or linux even in windows you can set alias for different registries                  NPM ALIASES                       alias npm-default  npm config set registry https   registry npmjs org  alias npm-sinopia  npm config set registry http   localhost 4873

User · Answer

On version 4 4 1  if you can change package name  use   npm config set  myco registry http   reg example com   Where  myco is your package scope    You can install package in this way   npm install  myco my-package   For more info  https   docs npmjs com misc scope

User · Answer

My approach was to make a slight command line variant that adds the registry switch   I created these files in the nodejs folder where the npm executable is found   npm- cmd    ECHO OFF npm --registry https   registry npmjs org      npm-      bin sh  npm  --registry https   registry npmjs org        Now  if I want to do an operation against the normal npm registry  while I am not connected to the VPN   I just type npm- where I would usually type npm   To test this command and see the registry for a package  use this example   npm- view lodash   PS  I am in windows and have tested this in Bash  CMD  and Powershell  I also

User · Answer

I use Strongloop s cli tools for that  see https   strongloop com strongblog switch-between-configure-public-and-private-npm-registry  for more information  Switching between repositories is as easy as   slc registry use  lt name gt

User · Answer

Since it has been a couple years and it doesn t seem possible to do this  using npm alone   a solution to this problem is to use the Nexus Repository Manager  from Sonatype    Nexus supports multiple repositories  lets you order them  and also proxies caches to improve speed   A free version and pro paid version exist   The feature that supports this is described at  https   help sonatype com repomanager3 node-packaged-modules-and-npm-registries  The relevant information is duplicated below so if when the above URL link stops working the information is still here      A repository group is the recommended way to expose all your npm registries repositories from the repository manager to your users  without needing any further client side configuration  A repository group allows you to expose the aggregated content of multiple proxy and hosted repositories with one URL to npm and other tools    It lets you create private npm registries     A private npm registry can be used to upload your own packages as well as third-party packages     And     To reduce duplicate downloads and improve download speeds for your developers and CI servers  you should proxy the registry hosted at https   registry npmjs org  By default npm accesses this registry directly  You can also proxy any other registries you require    So a quick bulleted list of things you do to get this working is    Install Nexus Create a local private repo  or point to your private repo on another server  Create a GROUP that lists your private repo  and the public repo  Configure your  HOME  npmrc file to point to the  GROUP  just created  Publish your private npm packages to the local repo  Users now can run a one time setup    npm config set registry https   nexus content groups GROUP   Then users can install both public or private packages via npm install   npm install my-private-package npm install lodash any-other-public-package    And both your public and private packages can be installed via a simple npm install command   Nexus finds the package searching each repo configured in the group and returns the results    So npm still thinks there is just one registry but behind the curtain there are multiple repos being used   IMPORTANT NOTE  When you publish your components  you ll need to specify the npm publish --registry https   nexus content repositories private-repo my-private-package command so your package is published to the correct repo

User · Answer

Some steps you can try   its how we do it at my workplace    Create a registry group with two  or more  repository source address  One would be your internal private and the other a proxy to npmjs giving priority to the internal one  Make this group your registry in the  npmrc file  This way npm will always try to get it from the internal one  if not found get it from the proxy   Hope that helps

User · Answer

For anyone looking also for a solution for authentication  I would add on the scoped packages solution that you can have multiple lines in your  npmrc file     internal-npm example com 8080   authToken xxxxxxxxxxxxxxx   registry npmjs org   authToken yyyyyyyyyy   Each line represents a different NPM registry

User · Answer

As of 13 April 2020 there is no such functionality unless you are able to use different scopes  but you may use the postinstall script as a workaround  It is always executed  well  after each npm install   Say you have your  npmrc configured to install  foo-org foo-pack-private from your private github repo  but the  foo-org foo-pack-public public package is on npm  under the same scope  foo-org    Your postinstall might look like this    scripts                  postinstall    mv  npmrc  npmrcc  amp  amp  npm i  foo-org foo-pack --dry-run  amp  amp  mv  npmrcc  npmrc       Don t forget to remove  foo-pack foo-org from the dependencies array to make sure npm install does not try and get it from github and to add the --dry-run flag that makes sure package json and package-lock json stay unchanged after npm install

User · Answer

I encounter the same problem when my company set up its own registry  so I heavily rework on proxy-registry into proxy-multi-registries to solve this problem  Hope it will also helps you

User · Answer

You can use multiple repositories syntax for the registry entry in your  npmrc file   registry http   serverA url repository-uri    serverB url repository-uri    serverC url repository-uri   authToken 00000000-0000-0000-0000-0000000000000   registry npmjs org    That would make your npm look for packages in different servers

[node.js] Is there any way to configure multiple registries in a single npmrc file

Examples related to node.js

Examples related to npm