Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The on event for `connect` does not work
See original GitHub issuengx-socket-io coming from ng-socket-io library.
The socket on event for connect doesn’t seem to work.
The functionality used to work in the previous package.
this.socket.on('connect', () => {
console.log('connect')
});
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
socket.io - 'connect' event does not fire on the client
I am trying to get started with node.js and socket.io. I have a very (very) simple client-server test application and i can't get...
Read more >[SOLVED] Windows could not connect to the System Event ...
On your keyboard, hold down the Windows logo key and press R to invoke the Run box. · Type cmd, then press Shift...
Read more >How to Troubleshoot Facebook App Event Setup Tool
You have your app open on your mobile device. If your app was already open when you tried to connect to Events Manager,...
Read more >Event listeners not working? 3 key areas to troubleshoot
Are your event listeners not working as you'd expect? Here are 3 key areas to troubleshoot to help you get everything triggering as...
Read more >SharedWorkerGlobalScope: connect event - Web APIs | MDN
The connect event is fired in shared workers at their SharedWorkerGlobalScope when a new client connects. This event is not cancelable and does...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Release two new versions to fix this problem.
Release v3.3.1 for developers who are not using socket-io v4 on their server and v4.0.0 for the developer using it.
| thou i would recommend to the people working on this package to rename 3.3.0 to 4.0.0 to prevent issues similar to this
Estimating from the high number of traffic on this issue that seems like a good idea, @rodgc ?