Releases: SocketCluster/socketcluster-client
Releases · SocketCluster/socketcluster-client
v16.0.1
v13.0.0
- An error event will be emitted on the socket if the user tries to emit a reserved event on that socket.
- Fixed a bug with
autoConnect: false
being ignored whensocketCluster.create(...)
was called a second time and it tried to reuse the same multiplexed socket as before (the issue could only happen ifmultiplex
was true in both calls) - In the second call it would try to auto connect; even thoughautoConnect
was false. - Renamed
SCSocket
toSCClientSocket
.
v12.0.0
Breaking changes:
- The 'authenticate' event will now also trigger when the
authToken
changes (not just the first time) - This change was done so that the client side SCSocket would be more consistent with the behavior of the server side SCSocket. This change affects scenarios where one user's authToken overrides a previously logged in user's authToken (e.g. If a new user logs in while another user account is already logged into the same machine/browser). - The
authTokenChange
event was removed; this event is no longer necessary since it is now equivalent to listening to both theauthenticate
anddeauthenticate
events.
v11.2.0
- Added support for new
pingTimeoutDisabled
option on the client which can be used to prevent the client socket from disconnecting itself because of a ping timeout. - Improved memory efficiency by clearing all pending timeouts as soon as the underlying transport socket closes (instead of allowing them to timeout on their own).
v11.0.0
v10.1.2
v10.0.0
- The
socketCluster.connect(options)
method was renamed tosocketCluster.create(options)
(theconnect
alias is still available but deprecated). - Calling
socket.destroy()
is now supported and is the same as callingsocketCluster.destroy(socket)
. - Non-multiplexed sockets now also show up in the
socketCluster.clients
(previously calledsocketCluster.connections
) object/map.
Breaking changes:
- The
socketCluster.connections
object was renamed tosocketCluster.clients
- The
socketCluster.destroy(...)
method now takes asocket
object as argument (instead of anoptions
object).