You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I have no idea what the cause of this issue is. There was this issue socketio/socket.io#2381 but running socket.io 2 in a node sandboxe works just fine using jasmine.
uWS is also not the issue. It works fine in jest.
Note: for support questions, please use one of these channels: stackoverflow or slack
You want to:
Current behaviour
If running engine 3.1.3 ( and also socket.io 2 ) in jest, the client is not able to connect to the server.
Same test with jasmine works fine.
Steps to reproduce (if the current behaviour is a bug)
Since there are a couple of variants to consider; I created a repository:
https://github.com/jeduden/jest-issue
Expected behaviour
Be able to use engine.io 3 / socket.io 2 within jest test.
Setup
Other information (e.g. stacktraces, related issues, suggestions how to fix)
Please refer to the repo: https://github.com/jeduden/jest-issue .
It includes logs, example code and variants of the issue.
Currently, I have no idea what the cause of this issue is. There was this issue socketio/socket.io#2381 but running socket.io 2 in a node sandboxe works just fine using jasmine.
uWS is also not the issue. It works fine in jest.
Also filed this issue in the jest repo: jestjs/jest#4815
The text was updated successfully, but these errors were encountered: