Hi, In our git repository we check-in all dependencies and devDependencies that are defined in our package.json. However, once we deploy to our site, we only copy over dependencies, but not the devDependencies. This keeps our deployment as small as possible.
This process ensures that the version we run on the site is always the same we have locally for development, minus the devDependencies that are not present in production. Now, if I understand npms algorithm during install correctly, it will not install the same module dependency twice if it already exists in the "family" of modules installed. And I am wondering if this includes devDependencies as well. Here is the issue: If I have a devDependency that depends on "something 2.0.0" and a dependency that depends on "something 2.0.0", npm would lift up "something 2.0.0" so that it can be shared between both modules. However, in production we do not ship the devDependencies, so could we end up missing some modules? Or is npm smart enough to not share dependencies between devDependencies and normal dependencies? Thanks, Ben -- -- 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.
