If you're worried about non-compatible changes, you can use `npm shrinkwrap` to pin down those versions.
There is no standard practice here, just do what you think is best for you. On Friday, November 15, 2013 2:36:29 PM UTC+4, Sam Darwin wrote: > > > when deploying node.js code onto production servers, we run "npm install" > as one of the steps. > > is this standard practice? what is the recommended procedure? > > the problem is that "npm install" downloads a million little modules, and > if even one module is buggy that morning, because the developers of that > module made a mistake, or released a non-compatible change the day before, > the production server will be broken. > > > -- -- 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.
