Comparing changes

This reverts commit f78a575. This commit contains a breaking change which deviates from semver, which we try to follow as closely as possible. That's why this change is reverted and we will rather suggest users to upgrade to v3. Related: #3741

Diff: 2.4.0...2.4.1

Release notes: https://github.com/socketio/engine.io/releases/tag/3.6.0 Diff: socketio/engine.io@3.5.0...3.6.0

Related: #3095 Backported from 494c64e

Using an async operation with `io.use()` could lead to the creation of several instances of a same namespace, each of them overriding the previous one. Example: ```js io.use(async (nsp, auth, next) => { await anOperationThatTakesSomeTime(); next(); }); ``` Related: #4136 Backported from 9d86397

The Socket instance is only considered connected when the "connection" event is emitted, and not during the middleware(s) execution. ```js io.use((socket, next) => { console.log(socket.connected); // prints "false" next(); }); io.on("connection", (socket) => { console.log(socket.connected); // prints "true" }); ``` Related: #4129 Backported from 02b0f73

Calling `socket.join()` after disconnection would lead to a memory leak, because the room was never removed from the memory: ```js io.on("connection", (socket) => { socket.disconnect(); socket.join("room1"); // leak }); ``` Related: - #4067 - #4380 Backported from 18f3fda

Release notes: https://github.com/socketio/socket.io/releases/tag/2.5.0 Diff: 2.4.1...2.5.0

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comparing changes

Open a pull request

Commits on Jan 7, 2021

Commits on Jun 26, 2022

This comparison is taking too long to generate.