Here’s the #3 edition of our Monthly update.
So, what’s new in the Socket.IO ecosystem?
Wait, already v4?
Yes, but the upgrade should be a lot easier than from v2 to v3, since the two breaking changes only impact the API on the server side.
The most important breaking change is related to broadcasting: calling
to() or any other broadcast modifier will now return an immutable object.
Previously, the modifiers were saved on the
io instance directly, which could lead to surprising behaviors:
You were also not able to reuse the operator:
const operator = io.to("room1");
Even more surprising, with asynchronous code:
io.to("room3").emit("details", await fetchDetails()); // unspecified behavior: maybe in room3, maybe to all clients
Starting with v4.0.0, you can now use
const operator = io.to("room1").except("room2");
This release also brings some interesting new features, like the
Please check the migration guide here.
The Redis adapter (for broadcasting packets with multiple Socket.IO servers) and the Redis emitter (for broadcasting packets from another Node.js process) have been updated in order to support the new features of the v4 release.
For example, the
socketsJoin method will work across Socket.IO servers:
// make all Socket instances join the "room1" room
More information can be found here.
The documentation continues to be improved.
A new example project has been added in the “Get started” section, with middlewares and rooms: Private messaging
As usual, if you find a typo or think that some details are missing, please open an issue here: https://github.com/socketio/socket.io-website
- a continuous focus on the documentation (additional code examples, extended guide, …)
- additional tooling around Socket.IO