Agreed!
I know one must read the fabulous manual, but I still managed to lost a couple of hours (and hair) figuring out why the hell my code wasn't working.
Totally my fault, but I would have liked it a lot if I was thrown some warning saying "Those events are reserved, try something else".

PR is welcome, as usual!

I already considered that, but I failed to find a repository that contains the website source. Maybe I'm just incompetent or was too tired, can you point me to it?

I just started looking at this (see here) but this comes with a need of something like a verbose parameter. Plus I'm pretty sure this is also triggered by those "internal" events. And finally console.warn.calledWith() does not exist in expect.
Still need some work ...

Closing due to inactivity, please reopen if needed.

It's hard to know if the issue was fixed or not, due to #1054 (the page renders nothing currently).

Is ping/pong not some real basic shit in networking? why the hell would they not be documented? There are ping and pong events sent back and fourth between the server and client automatically (upon socket connection)? If so, how do i look at these events and their timestamps to measure latency?

Can we reopen this, I agree with ForgeableSum. We should have more documentation.

Well it's already documented https://github.com/socketio/socket.io-client/blob/master/docs/API.md#event-ping-1 , I was struggling for hours trying to receive data from a custom ping event sent by my client, it seems that you can't override this event. 😅

Ugh. I just burnt loads of time here. RTFM.

As this page is now the top result when searching for 'socket.io ping pong events':

If you are making your own 'ping' and 'pong' events and they are behaving strangely, it is because socket.io is using those events internally to monitor the connection. Rename your own events to something else like 'my-ping' and 'my-pong' and they will work as expected.

@dmlo please note that this is not true anymore in version > 3.0.0, you can totally use ping and pong in your application.

Reference:

• https://socket.io/docs/v4/emit-cheatsheet/#Reserved-events
• https://socket.io/docs/v4/migrating-from-2-x-to-3-0/

Using a reserved event will now throw an error, as suggested in a comment above:

// will throw an error
socket.emit("connect");

@darrachequesne Thank you for the clarification. I am indeed using 2.4 with NestJS. They suggest support for 3.0 is coming in the next major version.