Interesting discussion about the move from npm to checking in modules. At my workplace we went the opposite direction :) We aren't using a private npm repository though... I don't think that would be worth it for our case.
This particular question is about an open source module, though. I'm going to play with the suggestion from Ruben... but it looks like it adds a dependency on git. Which is probably ok, but conceivably someone could be using another source control system and not have it installed. chris On Feb 9, 1:54 pm, Marco Rogers <[email protected]> wrote: > If you're building an app, check in your dependencies. Take npm out of the > equation (mostly) :) > > http://eng.yammer.com/blog/2012/1/4/managing-nodejs-dependencies-and-... > > :Marco -- 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
