Closed Xaekai closed 3 years ago
It warrants investigation whether socket.io 3.0 is backwards compatible for existing clients or not. If it's a breaking change, I'd be tempted to just go ahead and migrate to plain uWebSockets.js instead.
socket.io 3 uses engine.io 4 which is a breaking protocol change, so this will definitely break existing socket.io clients.
Apparently socket.io 4 is already out now. I need to check if it has any backwards compatibility for 2.x clients.
I was surprised you didn't bump it up to 2.4.1 in the meantime when you did that recent dependency bump.
It does look like there is some sort of compat flag https://socket.io/docs/v3/server-initialization/#allowEIO3
I was surprised you didn't bump it up to 2.4.1 in the meantime when you did that recent dependency bump.
That was because they made breaking changes to the server initialization that I didn't feel like fixing at the time.
Version 3 is out, and it brings a new wildcard event emitter which would be super handy for simplifying the bot.