Thanks Matt, That makes sense. I guess this happens when the modules has a dependency on a specific version or range of versions of a modules.
Now I'll take ryandesign's advice and move on. On Wednesday, March 21, 2012 1:19:18 AM UTC+1, Matt wrote: > > I believe the reason it does this is so that packages may have > differently-versioned dependencies. Right *now* they're the same, but > let's say the top-level package upgraded to a newer version of formidable > that connect was not prepared to support. It would be necessary for connect > to have its own copy of the older version of the package. > > Hope that makes a little more sense! > > -Matt > -- 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
