Releases: ably/ably-js
Releases · ably/ably-js
v2.4.0
v2.3.2
v2.3.1
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
v2.2.0
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
*
andprivileged-headers
values forTokenParams.capability
field #1765 - Add support for unique
logHandler
per Ably client by removing the global effects of settinglogHandler
andlogLevel
#1764 - Change
updateStatus
function returned byusePresence
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 usingusePresence
hook #1761 - Fix
Unable to enter presence channel while in suspended state
errors withusePresence
#1781 - Fix
Can't resolve 'ably'
error for environments that don't supportexports
field inpackage.json
yet #1782
v2.0.4
v2.0.3
- Improve error message displayed when trying to use
Ably.Realtime
instance in the Vercel Edge runtime #1736 - Fix to allow
ErrorInfo
export to be accessed as a named export in ESM and when using commonjs interop #1741 - Fix
ReferenceError: self is not defined
error when running Jest tests in React Native using ably-js #1738 - Fix
httpMaxRetryDuration
client option didn't actually limit max elapsed time for rest fallback host retries #1721 - Fix default value for
httpRequestTimeout
client option was wrongly 15 seconds instead of expected 10 seconds #1721