title: Why doesn't npm install correctly build dependency from a fork of a package on npm?
body: <p>I have a project that uses an older version of <a href="https://github.com/react-bootstrap/react-bootstrap/tree/v0.13.3" rel="noreferrer">react-bootstrap</a></p>
  
  <p>in my package.json I had</p>
  
  <pre><code>"react-boostrap": "^0.13.3"
  </code></pre>
  
  <p>And there is a bug in there that is causing an issue, the fix for it is very simple so I forked the repo, rolled back to the commit for v0.13.3 doing:</p>
  
  <pre><code>git reset --hard &lt;commit-hash&gt;
  </code></pre>
  
  <p>made my 1 line fix, then force pushed back to my fork.</p>
  
  <p>Then I updated my package.json in the main project to point to my fork:</p>
  
  <pre><code>"react-boostrap": "mygithubrepo/react-bootstrap"
  </code></pre>
  
  <p>I deleted the node_modules directory and ran <code>sudo npm cache clear</code> to make sure everything was nice and fresh. Then I ran <code>npm install</code> which did pull down my version of react-bootstrap from the repo.</p>
  
  <p>However, the version it now pulls down isn't in the same format in the node_modules folder. Essentially, it doesn't seem as if it's built the project.</p>
  
  <p>If I use:</p>
  
  <pre><code>"react-boostrap": "^0.13.3"
  </code></pre>
  
  <p>then the node_modules folder contains the built code like so:</p>
  
  <pre><code>+node_modules
  --+react_bootstrap
  ----+utils
  -----Acordion.js
  etc.....
  </code></pre>
  
  <p>But when I point it to my forked version of the repo:</p>
  
  <pre><code>"react-boostrap": "mygithubrepo/react-bootstrap"
  </code></pre>
  
  <p>Then I get just the source repo structure in node modules (and it doesn't seem to be built)</p>
  
  <pre><code>+node_modules
  --+react_bootstrap
  ----+docs
  ----+ie8
  ----+src
  -------+utils
  --------Acordion.jsx
  ........etc.....
  ----+tools
  etc.....
  </code></pre>
  
  <p>Now when I reference react bootstrap using <code>require('react-bootstrap')</code> then it doesn't work (because the files haven't been built).</p>
  
  <p>So what is different between me pointing to the file on npmjs rather than on github?  There isn't any prepublish/publish/postpublish script in react-bootstrap package.json so I'm not sure if they manually built it before pushing to npmjs.</p>
  
  <p>Basically, I need to get my forked version automatically built when I run <code>npm install</code> on my main project. Any ideas?</p>
  
  <p><strong>Edit 1</strong></p>
  
  <p>The errors I get running <code>npm install</code> on the main project repo after updating my fork of react-bootstrap as per Jonathan Muller's answer below:</p>
  
  <pre><code>&gt;&gt; Local Npm module "grunt-contrib-uglify" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-amd-wrap" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-react" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-contrib-clean" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-contrib-watch" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-contrib-copy" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-browserify" not found. Is it installed?
  &gt;&gt; Local Npm module "grunt-contrib-requirejs" not found. Is it installed?
  Warning: Task "clean:amd" not found. Use --force to continue.
  
  Aborted due to warnings.
  </code></pre>