3.0.0 (2020-11-05)

Code Refactoring

• rename ERROR to CONNECT_ERROR (13e1db7)

Features

• emit an Error object upon middleware error (0939395)
• add bundle with msgpack parser (71d6048)
• add support for catch-all listeners (55f464f)
• add volatile events (7ddad2c)
• move binary detection back to the parser (1789094)
• add ES6 module export (cbabb03)
• do not reuse the Engine.IO id (bbe94ad)
• remove the implicit connection to the default namespace (249e0be)
• split the events of the Manager and Socket (132f8ec)
• throw upon reserved event names (6494f61)

BREAKING CHANGES

• the Socket instance will now emit a "connect_error" event instead of "error" (which is not a reserved event anymore)

// before
socket.on("error", () => {});

// after
socket.on("connect_error", () => {});

• the Socket#binary() method is removed, as this use case is now covered by the ability to provide your own parser.

• the Socket instance will no longer forward the events of its Manager

Those events can still be accessed on the Manager instance though:

socket.io.on("reconnect", () => {
  // ...
});

3.0.0-rc4 (2020-10-30)

Features

• emit an Error object upon middleware error (0939395)

3.0.0-rc3 (2020-10-26)

Code Refactoring

• rename ERROR to CONNECT_ERROR (13e1db7)

Features

• add bundle with msgpack parser (71d6048)
• add support for catch-all listeners (55f464f)
• add volatile events (7ddad2c)

BREAKING CHANGES

• the Socket instance will now emit a "connect_error" event instead of "error" (which is not a reserved event anymore)

// before
socket.on("error", () => {});

// after
socket.on("connect_error", () => {});

3.0.0-rc2 (2020-10-15)

Features

• move binary detection back to the parser (1789094)

BREAKING CHANGES

• the Socket#binary() method is removed, as this use case is now covered by the ability to provide your own parser.

3.0.0-rc1 (2020-10-13)

Features

• add ES6 module export (cbabb03)
• do not reuse the Engine.IO id (bbe94ad)
• remove the implicit connection to the default namespace (249e0be)
• split the events of the Manager and Socket (132f8ec)
• throw upon reserved event names (6494f61)

BREAKING CHANGES

• the Socket instance will no longer forward the events of its Manager

Those events can still be accessed on the Manager instance though:

socket.io.on("reconnect", () => {
  // ...
});

2.3.1 (2020-09-30)

The debug dependency has been reverted to ~3.1.0, as the newer versions contains ES6 syntax which breaks in IE browsers.

Please note that this only applied to users that bundle the Socket.IO client in their application, with webpack for example, as the "official" bundles (in the dist/ folder) were already transpiled with babel.

For webpack users, you can also take a look at the webpack-remove-debug plugin.

Bug Fixes

• fix reconnection after opening socket asynchronously (#1253) (050108b)

2.3.0 (2019-09-20)

The minor bump is matching the bump of the server, but there is no new feature in this release.

2.2.0 (2018-11-29)

Bug fixes

• remove any reference to the global variable (related: https://github.com/socketio/socket.io-client/issues/1166)

2.1.1 (2018-05-17)

Bug fixes

• fire an error event on middleware failure for non-root namespace (#1202) (0fe9439)

2.1.0 (2018-03-29)

Features

• add a 'binary' flag (#1194) (74893d5)

// by default, the object is recursively scanned to check whether it contains some binary data
// in the following example, the check is skipped in order to improve performance
socket.binary(false).emit('plain-object', object);