On Thursday, May 2, 2013 1:53:11 PM UTC-4, Matt Sergeant wrote: > On Thu, May 2, 2013 at 1:45 PM, Laurie <[email protected] > <javascript:>>wrote: > >> This is for work; we want to manage our internal modules with npm, but >> the code is proprietary so can't be published to the central registry. A >> private registry is the cleanest solution (vs. f.e. using url dependencies >> or something). >> > > We just do this with private github repos and URL dependencies pointing > direct to the github repo. >
Unfortunately, we don't use git. I could do something similar with `npm pack` and a shared file volume, but then we lose `npm publish` and, more significantly, fuzzy version matching. Propagating updates to a module with `npm version && npm publish` on one side, and `npm update` on the other, keeps things nice and simple :-) L. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
