Describe the bug
When running Angular tests with Karma, this library can now double close a Node server on 4.8.2 leading to .ERR_SERVER_NOT_RUNNING. I believe this issue was mentioned as being known about and that they would handle it in v5 in #4546 however 4.8.2 and #5344 seem to have caused the issue prematurely.
I was able to work around this issue by pinning Karma's metadependency. This appeared to fix the issue.
"overrides": {
"karma": {
"socket.io": "4.8.1"
}
}
I believe this is now a bug with socket.io integrating with other libraries.
To Reproduce
Starting tests in an Angular application and then closing the server causes ERR_SERVER_NOT_RUNNING.
Expected behavior
I expect socket.io to not close a closed HTTP server.
Describe the bug
When running Angular tests with Karma, this library can now double close a Node server on 4.8.2 leading to .ERR_SERVER_NOT_RUNNING. I believe this issue was mentioned as being known about and that they would handle it in v5 in #4546 however 4.8.2 and #5344 seem to have caused the issue prematurely.
I was able to work around this issue by pinning Karma's metadependency. This appeared to fix the issue.
I believe this is now a bug with socket.io integrating with other libraries.
To Reproduce
Starting tests in an Angular application and then closing the server causes ERR_SERVER_NOT_RUNNING.
Expected behavior
I expect socket.io to not close a closed HTTP server.