For the Googlers of the future that reach this thread: the answer depends on the nature of your project.
- *Do** track* `node_modules` in your repo if you are deploying an app. - *Do not** track* `node_modules` in your repo if your project is a reusable package meant to be consumed by other projects. See this post <http://www.futurealoof.com/posts/nodemodules-in-git.html>for an explanation as to why this is the best practice. Also, it's a good idea to register *all* dependencies in your `package.json`: a dependency can be any git repo, not only ones published in the npm registry. On Sunday, December 4, 2011 3:56:52 PM UTC-5, deitch wrote: > > You are building an app, it has dependencies on lots of modules that > you install via npm. But versionizing those in git seems redundant. > What do people here do? Do they keep node_modules as tracked part of > git? Or do they put it in .gitignore, and if so, then how do you know > which versions and dependencies you have? > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com 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 nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
