Closed spmason closed 11 years ago
The cache, if it were to be done, should be configurable (I specifically would never need cache), but the fallback to the main repo would be incredibly awesome :+1:
I don't think this feature fits into Reggie.
BTW there are already projects implementing both private registry and npm cache: shadow-npm, nopar and probably one or two more that I couldn't quickly google out.
That was the response I thought I'd get, to be honest, and that's fine by me really
One thing, where's your source that someone is working on multiple registries? From what I can find there hasn't been movement on it for a while (https://github.com/isaacs/npm/pull/100, https://github.com/isaacs/npm/issues/1401, https://github.com/isaacs/npm/pull/3093)
One thing, where's your source that someone is working on multiple registries? From what I can find there hasn't been movement on it for a while (isaacs/npm#100, isaacs/npm#1401, isaacs/npm#3093)
Well, it's me who is working on multiple registries. I guess I should have announced it sooner. Anyway, I commented on isaacs/npm#1401 so that people know there is some progress being made.
So you could have Reggie host your private packages and fall back to the main repo for public stuff.
It could even "cache" packages locally itself, to speed things up
Is this something reggie would/should ever do?