title: npm and node slow to exit on Windows
body: <p>I have a build process using npm with several tasks registered in a chain.</p>
  
  <p>package.json looks like this (the http/https stuff is because of a proxy server certificate that upsets npm):</p>
  
  <pre><code>  "scripts": {
      "git-config": "git config --global --replace-all url.\"https://\".insteadOf git://",
      "bower-install": "node_modules/.bin/bower install",
      "bower": "npm run git-config &amp;&amp; npm run bower-install",
      "build": "npm config set registry http://registry.npmjs.org/ &amp;&amp; npm config set strict-ssl false &amp;&amp; npm install &amp;&amp; npm run bower &amp;&amp; node build-bundles"
    },
  </code></pre>
  
  <p>Every time npm or node is launched, there seems to be about a .5 second hang to launch, and another 1.5 second hang AFTER the command has finished but before the npm/node process exits. In the above script, there are many calls to npm/node, and this ends up adding 15-20 seconds onto our build time (even if there are no changes).</p>
  
  <p>Is there any way to:</p>
  
  <ul>
  <li>Eliminate at least the 2 second hang before npm/node exits</li>
  <li>Make the above script(s) only execute when one of the project files changes (I do not want to use watchify)</li>
  <li>Otherwise improve the speed of these scripts</li>
  </ul>
  
  <p>Please note that this question doesn't have anything to do with the speed of npm install, package caching, package download speed or the like.</p>
  
  <p>Thanks.</p>