ng serve error 'This socket is closed'

[ninodinatale]

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.

[manwaring]

I get the same error when I run ng init - the command hangs, after manually exiting it returns the same message

Im also getting the same error too. I really hope it's nothing any our end.

[nullhart]

I am also having this error. (Windows 10 x64)

[manwaring]

It looks like the cause might be in Node 7.1.0 itself: nodejs/node#9542

[Marianogboo]

I am also having this error. started after i installed node 7.1. My project was fine until this.

[Nhiyhe]

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

[alberthoekstra]

Nhiyhe is right, after installing the node 6.9.1 LTS it's all good!

[ninodinatale]

can confirm that as well.

[tebeco]

is the issue really in NodeJS ? or should Angular CLI be updated ?
seems to work in company without angular cli to serve either Angular 1.x or React

[OdaiTu]

i have nodejs : 7.1.0
npm : 3
and install npm install -g angular-cli just now
and i have the same error when write command : ng serve
so what is the solution plz :(

[OdaiTu]

lol

the problem resloved by uninstall the node :7.1.0 and install the node :6.9.1
but i think this is not the right solution guys

[kylecollie]

Same problem - resolved by reverting to node 6.9.1

[uucly]

Same problem. Dont want to revert to node 6.9.1. Please quickfix

[seveves]

node v7.1.0 and same problem

[PacejetRepository]

same problem with v7.1.0