-
Notifications
You must be signed in to change notification settings - Fork 12k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ng serve error 'This socket is closed' #3102
Comments
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. |
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 ? |
i have nodejs : 7.1.0 |
lol the problem resloved by uninstall the node :7.1.0 and install the node :6.9.1 |
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 |
Reverted back to v6.9.1 LTS and errors gone. Very critical error on release |
Same Problem with 7.1 |
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?
Thanks in advance for your hard work. |
Same Problem here with 7.1 |
Thanks @ironmanwaring! |
This patch fix problem for me: |
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 |
NodeJS 7.2 release: This is a security release impacting Windows 10 users.
2016-11-23 7:22 GMT+02:00 Steven U notifications@github.com:
|
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. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
OS?
Windows 10
Versions.
angular-cli: 1.0.0-beta.19-3
node: 7.1.0
os: win32 x64
Repro steps.
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.
Mention any other details that might be useful.
The text was updated successfully, but these errors were encountered: