Socketcluster Client Versions Save

• Improvements to the Consumer API. See https://socketcluster.io/docs/consumers/

• 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 when socketCluster.create(...) was called a second time and it tried to reuse the same multiplexed socket as before (the issue could only happen if multiplex was true in both calls) - In the second call it would try to auto connect; even though autoConnect was false.
• Renamed SCSocket to SCClientSocket.

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 the authenticate and deauthenticate events.

• 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).

• Throw error if the user passes invalid combinations of hostname, host and port arguments.
• Added nore tests.

• More detailed socket close messages.
• Upgraded dependencies.

• The socketCluster.connect(options) method was renamed to socketCluster.create(options) (the connect alias is still available but deprecated).
• Calling socket.destroy() is now supported and is the same as calling socketCluster.destroy(socket).
• Non-multiplexed sockets now also show up in the socketCluster.clients (previously called socketCluster.connections) object/map.

Breaking changes:

• The socketCluster.connections object was renamed to socketCluster.clients
• The socketCluster.destroy(...) method now takes a socket object as argument (instead of an options object).

Fixed issue with missing callback error in specific situations.

Added gulp build process. Fixed React Native error related to addEventListener function being undefined.

Added subscription batching - This allows the client to subscribe to multiple channels using a single WebSocket frame for a performance boost.

Breaking change:

Bug fix: the 'raw' event argument will now always be a string. There was an issue in older versions where a JSON string would be cast to an object.