v2.6.0

Full Changelog: 2.5.0...2.6.0

What's Changed

• Removed a build check that prevented referencing branch builds in package.json. It is now possible to point npm at specific branches of ably-js. #1927
• Presence will now only emit a LEAVE event if a member was present in the presence set to begin with. #1918
• The experimental attributes on the Message type to support edits and deletes have been updated and renamed. #1923

v2.5.0

Full Changelog: 2.4.1...2.5.0

What's Changed

• Exposed the new Message attributes needed to support upcoming features, such as updates, deletions and annotations in the Ably service. #1888 #1916

v2.4.1

Full Changelog: 2.4.0...2.4.1

What's Changed

• Fix usePresence hook wasn't leaving presence if component unmounted during channel attaching state #1884

v2.4.0

Full Changelog: 2.3.2...2.4.0

What's Changed

• Add wsConnectivityCheckUrl client option #1862
• Push plugin is now available to be loaded via a CDN link #1861

v2.3.2

Full Changelog: 2.3.1...2.3.2

What's Changed

• Fix websocket reconnection can get stuck in a disconnected/connecting loop under specific network conditions #1855
• Fix fetchRequest implementation didn't work with checkConnectivity #1856

v2.3.1

Full Changelog: 2.3.0...2.3.1

What's Changed

• Export EventEmitter so we can use it in other SDKs in #1819
• Fix missing ablyId argument to useConnectionStateListener in #1821

v2.3.0

With this release, ably-js clients can now be activated as a target for web push notifications. See our official docs for instructions on how to start publishing web push notifications using Ably.

• Add support for web push activation #1775

v2.2.1

• Fix an occasion whereby a channel would attempt to automatically reattach from an inappropriate state #1802
• Update the type information so that ErrorInfo now extends the Error interface #1805

v2.2.0

• Add passing a log level as a second parameter to ClientOptions.logHandler function #1787
• Fix pings stacking when calling Connection.ping() if none ever succeed #1793

v2.1.0

With this release, Ably React Hooks have now moved to the general availability phase and are considered stable. Non-major version changes to the ably package won't include breaking changes for React Hooks going forward.

All changes:

• Add support for optional multiple recovery scopes via ClientOptions.recoveryKeyStorageName #1762
• Add wildcard * and privileged-headers values for TokenParams.capability field #1765
• Add support for unique logHandler per Ably client by removing the global effects of setting logHandler and logLevel #1764
• Change updateStatus function returned by usePresence hook to be async #1777
• Fix some of the errors thrown by ConnectionManager have misleading stack traces #1760
• Fix FetchRequest doesn't properly handle a 204 response #1773
• Fix Connection closed errors when using usePresence hook #1761
• Fix Unable to enter presence channel while in suspended state errors with usePresence #1781
• Fix Can't resolve 'ably' error for environments that don't support exports field in package.json yet #1782