Fredrik,
If you install a package at the higher level first, then npm will only
install a second copy if necessary. (In which case, even though it's
the same name, it's actually a different thing.)
Check out `npm ls` to see exactly what's installed where.
On Tue, Mar 20, 2012 at 17:24, Fredrik
I don't know if I just don't understand why and there is a really good
reason why it behaves the way it does.
I tried searching but I could not find anything relevant and the docs were
equally uninformative regarding this type of problem.
I might be a neat-freak but I dislike the same modules
On Mar 20, 2012, at 18:29, Fredrik Larsson wrote:
I don't know if I just don't understand why and there is a really good reason
why it behaves the way it does.
I tried searching but I could not find anything relevant and the docs were
equally uninformative regarding this type of problem.
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
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
