Jeff,

My company is running into the size issues you have cited.  I know this is 
an old thread, but I am wondering if you have ever resolved this with 
something like npm dedup

We currently have a 300 MB package in our company with many (> 20) 
duplicates of various module.

I am curious whether the use of consistent 'tags' would lead the community 
to solve this by encouraging modules to upgrade to 'tested', 'production 
ready' tags in the same time frame

Tony

On Thursday, January 5, 2012 5:13:33 AM UTC-8, Jeff Barczewski wrote:
>
> Jann,
>
> From tests I have run, it appears to me that if both copies exist (and are 
> not simply symbolic links to the same directory), node will load multiple 
> copies of these modules even if they are the same version of the module.
>
> So not only will do you have duplicate space on the file system and 
> possibly duplicate build time (for compiled modules), you also have 
> different copies of modules loaded into memory (even if they are the same 
> version) (and any data they cache).
>
> That's another reason I was suggesting it would be nice to have a tool 
> which can do just that (to clean/move duplicates to top or to move and 
> create symbolic links). I'm still working through some of the thought 
> process as to which approach might work better. 
>
> IMO, If you care about any of the above, you may want to remove the 
> duplicate directory from the lower paths.
>
> Jeff
>

-- 
-- 
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/d/optout.

Reply via email to