> and each project you start will have its own copy of this stuff I don't get why npm can't setup a content addressed shared repository, something à la m2/mave

> and each project you start will have its own copy of this stuff I don't get why npm can't setup a content addressed shared repository, something à la m2/maven. This seems like such a waste of space. I'm not up to speed with filesystems, but IMHO content-addressing by default should be a standard feature as well.