title: npm install and build of forked github repo
body: <p>I'm using a module for my angular app called angular-translate. However, I've had to make a few small modifications to the source code to get everything working the way I'd like, and now I want to persist those changes on <code>npm install</code>. A colleague suggested that I fork the repo of the source code and point to my forked repo as a dependency, which I've tried in these ways, e.g.</p>
  <pre><code>npm install https://github.com/myRepo/angular-translate
  npm install https://github.com/myRepo/angular-translate/archive/master.tar.gz
  </code></pre>
  <p>The first gives me a directory like this with no build. Just a package.json, .npmignore, and some markdown files</p>
  <pre><code>-angular-translate
     .npmignore 
     .nvmrc
      CHANGELOG.md 
      package.json
      etc
  </code></pre>
  <p>The second <code>npm install</code> gives me the full repo, but again I don't get a build like when I use the command <code>npm install angular-translate</code>.  I've seen some dicussion of running the prepublish script, but I'm not sure how to do this when installing all the modules.  I've also tried publishing the fork as my own module to the npm registry, but again I get no build, and I'm not sure that's the right thing to do...</p>
  <p>I apologise for my ignorance on the topic.  I don't have a huge amount of experience with npm. Would love to get some feedback on this issue.  It seems like it could be a  common enough issue when modifications need to be made to a package's source code? Maybe there's a better solution?</p>