Hi, 2013/8/2 Adam Crabtree <[email protected]>
> I can think of 3: > > 1. Semver. > > Pushing out a critical bug fix can be a liability if every project that > consumes that module, and all its parents must be updated. This is > exacerbated by node.js/npm's default behavior of deeply nested static > dependencies. > > 2. Private Forks of Public Modules > > Ability to publish private versions of public modules. Recently we wanted > a unique fix to forever-agent[1] which request depends upon. You could > achieve this via npm_shrinkwrap (I believe), but that would need to be done > on a per-project basis, whereas being able to publish a private forked > version, while still consuming the public request module is a little more > elegant because now everyone at your company who depends upon request, > doesn't need to remember to include an npm_shrinkwrap. > I hadn't thought of these two and now I can see the advantages. Thanks for the thorough response! Cheers, Santi -- -- 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.
