title: How do you fork and develop a globally installed Node.js NPM package?
body: <p>I'm trying to create a fix for a an NPM package that I rather enjoy, <a href="https://github.com/jnordberg/wintersmith" rel="nofollow">Wintersmith</a>. However, Wintersmith is supposed to be globally installed (executable with <code>wintersmith &lt;command&gt;</code>) and I can't seem to run it from the root of a project where I have it installed locally manually with <code>git clone &lt;my fork url&gt;</code> with something like <code>node ./node_modules/wintersmith/bin/wintersmith</code> without receiving path errors:</p>
  
  <pre><code>module.js:340
  throw err;
        ^
  Error: Cannot find module '../lib/cli/'
  at Function.Module._resolveFilename (module.js:338:15)
  at Function.Module._load (module.js:280:25)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at Object.&lt;anonymous&gt; (F:\web\wintersmith\node_modules\bin\wintersmith:3:1)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Function.Module.runMain (module.js:497:10)
  </code></pre>
  
  <p>The only way I can figure to properly develop and test this is by manually replacing my globally installed Wintersmith package with my forked version and then executing commands using that version to test whether or not my changes are working.</p>
  
  <p>Is there some workflow step that I'm missing when working with/developing global NPM packages?</p>