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.

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

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

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

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

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

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

can confirm that as well.

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

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 :(

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

Same problem - resolved by reverting to node 6.9.1

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

node v7.1.0 and same problem

same problem with v7.1.0

Same problem here, I had to revert to Node 6.9.1 (Win10-x64)

When I reinstalled angular-cli I notice the following WARNING. Might our problem be related to this in someway?

$>npm install -g angular-cli npm WARN deprecated graceful-fs@1.2.3: graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to graceful-fs@^4.0.0 as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.

Thanks in advance for your hard work.

Same Problem here with 7.1

Thanks @ironmanwaring!
Reverted to v6.9.1 and things went back to normal!

This patch fix problem for me:
nodejs/node#9542 (comment)

Yeap, reverted from 7.1 to 6.9 on windows 10 x64 and fixed it for me. Thanks!

workaround nodejs/node#9542 (comment)

same problam ... :-(

Ditto. Same problem when running ng serve
angular-cli: 1.0.0-beta.21
node: 7.1.0

@Fishrock123

NodeJS 7.2 release:
2016-11-22, Version 7.2.0 (Current), @Fishrock123

This is a security release impacting Windows 10 users.
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V7.md#notable-changesNotable
changes

libuv: Upgrade to v1.10.1 (cjihrig) [1.7.0] ng serve not properly killed on CTRL+C with yarn/npm #9647
deps: upgrade libuv to 1.10.1 nodejs/node#9647
- Fixed a potential buffer overflow when writing data to console on
  Windows 10. (CVE-2016-9551)

2016-11-23 7:22 GMT+02:00 Steven U notifications@github.com:

Ditto. Same problem when running ng serve
angular-cli: 1.0.0-beta.21
node: 7.1.0

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#3102 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AK6Qckx4f3Zn2NXGkgXLKgouAXyScpVLks5rA82RgaJpZM4Kuy7M
.

The same works for me, install node 6.9

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

As @ironmanwaring mentioned, this is an issue with node itself being tracked in nodejs/node#9542.

Solutions seem to be downgrade to 6.9, or go to 7.2.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

Navigation Menu

Repository navigation

ng serve error 'This socket is closed' #3102

Please provide us with the following information:

OS?

Versions.

Repro steps.

The log given by the failure.

Mention any other details that might be useful.

2 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

ng serve error 'This socket is closed' #3102

Description

Please provide us with the following information:

OS?

Versions.

Repro steps.

The log given by the failure.

Mention any other details that might be useful.

Activity

manwaring commented on Nov 10, 2016

nullhart commented on Nov 10, 2016

manwaring commented on Nov 11, 2016

Marianogboo commented on Nov 11, 2016

Nhiyhe commented on Nov 11, 2016

alberthoekstra commented on Nov 13, 2016

ninodinatale commented on Nov 13, 2016

tebeco commented on Nov 14, 2016

OdaiTu commented on Nov 14, 2016

OdaiTu commented on Nov 14, 2016

kylecollie commented on Nov 15, 2016

uucly commented on Nov 15, 2016

seveves commented on Nov 15, 2016

PacejetRepository commented on Nov 16, 2016

2 remaining items

davidema79 commented on Nov 17, 2016

cubidobusinesssolutions commented on Nov 18, 2016

vmourac commented on Nov 19, 2016

vfedoriv commented on Nov 19, 2016

feranto commented on Nov 20, 2016

arfeifei commented on Nov 21, 2016

yanai101 commented on Nov 22, 2016

StevenU8 commented on Nov 23, 2016

vfedoriv commented on Nov 23, 2016

plfgavilan commented on Dec 4, 2016

wei2learn commented on Dec 6, 2016

filipesilva commented on Dec 29, 2016

angular-automatic-lock-bot commented on Sep 6, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions