How to use private npm registry for specific module

Asked Jul 20 '17 at 17:02

Active Jul 20 '17 at 17:15

Viewed 227 times

Let's say we have a private registry (sinopia) and we have some private module there call "secret-lib"

What we are doing now is in a .npmrc add the following line:

registry=http://10.16.1.2:3333/

and package json:

dependancies: {
  "secret-lib": "^0.1.1",
}

However this makes that every other modules also being proxied through the private registry.

Is there a way to only go through the private registry when is fetching secrete-lib?

Additional information: The secret-lib also in a private repo managed by Lerna, so I cannot just do something like below because that's not the published module

dependancies: {
      "secret-lib": "git@my-company.io:libs/secret-lib.git^0.1.1",",
    }

edited Jul 20 '17 at 17:15

E_net4

27,810
13
101
139

asked Jul 20 '17 at 17:02

Yichz

9,250
10
54
92

Is not the same that was asked here? https://stackoverflow.com/a/38499150/308341 – Juan Picado Jul 25 '17 at 09:55
@juanpicado, no this is not the same. – Jamie Hill Aug 30 '17 at 14:55
@kossel, did you find a solution to this? – Jamie Hill Aug 30 '17 at 14:57
@JamieHill no, not yet, we are still using going through the private repo for everything – Yichz Aug 30 '17 at 22:06

How to use private npm registry for specific module

0 Answers0