title: How to reconcile global webpack install and local loaders
body: <p>My <code>package.json</code> includes webpack and some loaders:</p>
  
  <pre><code>"devDependencies": {
    "babel-core": "^5.2.17",
    "babel-loader": "^5.0.0",
    "jsx-loader": "^0.13.2",
    "node-libs-browser": "^0.5.0",
    "webpack": "^1.9.4"
  }
  </code></pre>
  
  <p>When I run <code>webpack</code> it's not in my path so it doesn't show as found. I installed it globally <code>npm install -g webpack</code> so the binary would appear in my path, but then it can't find the loader modules that were installed in <code>./node_modules</code> that it needs to process my dependency tree:</p>
  
  <pre><code>$ webpack --progress --colors --watch
  10% 0/1 build modules/usr/local/lib/node_modules/webpack/node_modules/webpack-core/lib/NormalModuleMixin.js:206
                  throw e;
                        ^
  Error: Cannot find module 'jstransform/simple'```
  </code></pre>
  
  <p>What is the preferred solution here? </p>
  
  <p>I can install my loaders globally, but I don't like that because of cross-project issues</p>
  
  <p>I can try to run webpack out of node_modules (not sure how to be honest, add it to <code>$PATH</code> for every project?)</p>
  
  <p>Or I can try to give my global webpack access to my node_modules folder, which also seems hacky. </p>
  
  <p>Have I done something wrong, or is there a better community-approved way around this maybe common problem?</p>