Closed xcoderzach closed 9 years ago
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 socket.io
working with express 3.x app by using next code:
var app = express();
var server = app.listen(4000);
var io = require('socket.io').listen(server);
Thanks @fedot. This fixes dnode with express@3.0.0alpha1 too :)
@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.
Here is the issue on connect https://github.com/senchalabs/connect/issues/500#issuecomment-4336487
I'm not sure if the issue is with socket.io or connect.