title: WebPack Dev Server doesn't start on Node.js 7.x
body: <p>I'm using <code>webpack@2.1.0-beta.27</code> and <code>webpack-dev-server@2.1.0-beta.11</code> last version packages. <code>webpack</code> works fine and it generates artifacts correctly.</p>
  
  <p>After that, I would need to know to deal with an issue I've not been able to handle with <code>webpack-dev-server</code>.</p>
  
  <p>I'm using three configuration files: </p>
  
  <ul>
  <li><a href="https://gist.github.com/jeusdi/134e19006a6f8da06bf4123c35d8a8a7" rel="nofollow noreferrer">webpack.common.js</a></li>
  <li><a href="https://gist.github.com/jeusdi/365e8cc433ef629d6246776dce0e3092" rel="nofollow noreferrer">webpack.dev.js</a></li>
  <li><a href="https://gist.github.com/jeusdi/919e6228b753cbe67f72edfd613a8c99" rel="nofollow noreferrer">webpack.prod.js</a></li>
  </ul>
  
  <p>The error message <code>webpack-dev-server</code> is dumping me:</p>
  
  <pre><code>#webpack-dev-server --config config/webpack.dev.js --progress --profile --co
  ntent-base src/
  Project is running at http://localhost:3000/
  webpack output is served from /
  Content not from webpack is served from D:\projects\living\user-platform\project\src
  404s will fallback to /
  events.js:160
        throw er; // Unhandled 'error' event
        ^
  
  Error: This socket is closed
      at WriteStream.Socket._writeGeneric (net.js:683:19)
      at WriteStream.Socket._write (net.js:734:8)
      at doWrite (_stream_writable.js:334:12)
      at writeOrBuffer (_stream_writable.js:320:5)
      at WriteStream.Writable.write (_stream_writable.js:247:11)
      at WriteStream.Socket.write (net.js:661:40)
      at Console.warn (console.js:51:16)
      at printErrorAndExit (D:\projects\living\user-platform\project\node_modules\source-map-support\source-map-support.js
  :406:11)
      at process.emit (D:\projects\living\user-platform\project\node_modules\source-map-support\source-map-support.js:419:
  16)
      at process._fatalException (bootstrap_node.js:292:26)
  [default] Checking started in a separate process...
  </code></pre>
  
  <p>I don't know why it crashes and what does the message mean?</p>
  
  <p>Any ideas?</p>