2

I'm adding several dependencies to a project that currently uses the default npm registry. Obviously the dependencies cannot be resolved since the packages are not found there.

I'm wondering if I can provide the packages via a folder or zip file instead and tell npm to bypass the registry for certain dependencies and take the packages directly from the folder. I want to avoid to setup my own registry.

lex82
  • 11,173
  • 2
  • 44
  • 69
  • Maybe you could just depend on the modules directly, using https://stackoverflow.com/questions/15806241/how-to-specify-local-modules-as-npm-package-dependencies? – Mormegil Jun 21 '17 at 09:31
  • Unfortunately this is not possible with reasonable effort because the packages I depend on have more dependencies that would have to be changed. – lex82 Jun 21 '17 at 09:45

1 Answers1

0

Sinopia seems to be a lightweight solution for the problem. It is a private repository server that allows to use private packages, cache the npmjs.org registry, and to override public packages.

Disclaimer: I haven't tried it because my problem was solved by another private registry I didn't know at the time of writing the question. However, maybe it helps someone else.

lex82
  • 11,173
  • 2
  • 44
  • 69