title: How can I handle Node.js dependencies in a project on git with NPM?
body: <p>I've run into this scenario quite a few times and still haven't found the answer.  I'm starting a new Node.js project, and this project will be dependent on some other libraries.  For sake of argument, let's say that some are purely JS libraries that could be added as git submodules in the new project, but some have pieces that need some extra effort (such as system dependencies that npm installs, or C libraries that must be compiled).</p>
  
  <p>What's the best way to start this project and add it to git, with the following two requirements:</p>
  
  <ul>
  <li>Other people's libraries aren't committed to our own repo, and are instead submodules or are pulled in dynamically and installed by npm.</li>
  <li>Not needing to have a big list of instructions that have to be followed just to clone the repo and have a working environment.  Running git submodules update --init --recursive is fine, running an npm command to read package.json and install the dependencies is fine (does such a command exist?), but forcing everyone to run through an "npm install <em>_</em>_" of every single dependency isn't ok, and I'd rather not use 'make' or 'ant' to do that if I don't have to.</li>
  </ul>
  
  <p>Any thoughts of the best way to do this?  It seems like such a simple, basic thing, but I couldn't find a single example of what I'm trying to do.</p>
  
  <p>Edit: Grammar</p>