angular-cli: ng serve error 'This socket is closed'

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Windows 10

Versions.

Please run ng --version. If there’s nothing outputted, please run in a Terminal: node --version and paste the result here:

angular-cli: 1.0.0-beta.19-3 node: 7.1.0 os: win32 x64

Repro steps.

Was this an app that wasn’t created using the CLI? What change did you do on your code? etc.

First it wasn’t working on my already existing project. I tried it with a test-project created with ng new, but still the same error.

The log given by the failure.

Normally this include a stack trace and some more information.

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 WriteStream.process.stderr.write (C:\Users\nino_\Documents\Angular\Projects\test_project\node_modules\angular-cli\lib\cli\index.js:32:27)
     at Console.warn (console.js:51:16)
     at printErrorAndExit (C:\Users\nino_\Documents\Angular\Projects\test_project\node_modules\awesome-typescript-loader\node_modules\source-map-support\source-map-support.js:406:11)
     at process.emit (C:\Users\nino_\Documents\Angular\Projects\test_project\node_modules\awesome-typescript-loader\node_modules\source-map-support\source-map-support.js:419:16)
     at process._fatalException (bootstrap_node.js:292:26)

Mention any other details that might be useful.


Thanks! We’ll be in touch soon.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 16
  • Comments: 30 (1 by maintainers)

Most upvoted comments

It looks like the cause might be in Node 7.1.0 itself: https://github.com/nodejs/node/issues/9542

I had the same problem, got it fixed by uninstall node 7.1.10 and installed node 6.9.1 LTS and it works…

Same problem with node 7.1. But the latest version 7.2 is working.