-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Socket.io doesn't work with connect 2.0.x #785
Comments
any idea when this is going to be updated to work with connect 2 /express 3? edit: after some digging, it seems like maybe the server events for connection, request, etc aren't making it out of connect. |
I've managed to get
|
@fedot THANK YOU SO MUCH. |
Any reasons to keep this issue "open"? There is a solution and corresponding bug senchalabs/connect#500 is closed for a long time... |
Maybe close when this is added to the readme / docs. |
Would be really great if this would be part of the socket.io readme. |
Use the new build env on Travis
Here is the issue on connect
senchalabs/connect#500 (comment)
I'm not sure if the issue is with socket.io or connect.
The text was updated successfully, but these errors were encountered: