Re: [nodejs] Re: Checking node_modules into git

I have been warming up to the way Netflix does their deployments. Each update is a full image, packaged as an Amazon Machine Image, ready to be inserted into an auto-scaling group. This technique can be abstracted to any VM-style cluster however. Since each images is pre-made, and ready to run on

[nodejs] Re: Checking node_modules into git

Using git submodules is my preferred style when writing applications. That way you point to an exact source code tree, all the while you keep their respective commit histories. I have a Git program (in Node.js) that manages the submodules for Node.js dependencies,

[nodejs] Re: Checking node_modules into git

Here's the article I wrote on checking in modules as well. I haven't really tried shrinkwrap, but it sounds like there are enough differences between the two approaches that you should explore both and see which one suits your needs best. I would employ shrinkwrap on a project where the deploy

[nodejs] Re: Checking node_modules into git

This is good approach, but only for final applications, you should never commit dependencies into repositories of resuable (generic) modules. I have great experience with that, and to me it's the *only* way to assure that installation of application is straightforward and the only way to make s

[nodejs] Re: Checking node_modules into git

For me checking in a npm-shrinkwrap.json gives all of the advantages of checking node_modules into git, with none of the drawbacks. That's my preferred solution. On Wednesday, December 26, 2012 7:05:45 PM UTC-5, José F. Romaniello wrote: > > Hi all, I have read few times that is better to checki