ably - npm Package Versions

2.10.1 (2025-07-16)

• Fix minimization issue with Next.js 15.4+ canary builds #2057

2.10.0 (2025-06-25)

• Add Channels.all to type declarations #2040
• Add ClientOptions.endpoint parameter and deprecate the environment, restHost and realtimeHost client options. See platform customization documentation for guidance on using the new endpoint parameter #1973

2.9.0 (2025-05-08)

Introducing Ably LiveObjects

With this release, ably-js now supports LiveObjects.

Ably LiveObjects enables effortless realtime synchronization of application state across multiple users and devices at any scale. When a LiveObject is updated, changes are automatically propagated to all subscribed clients in realtime, ensuring that everyone always sees the latest state.

The ably-js implementation for LiveObjects provides a simple, purpose-built API that handles realtime synchronization, persistence, and convergence behind the scenes.

See our official documentation to learn more about LiveObjects and how to start synchronizing your application state using Ably.

• Add support for Ably LiveObjects #2007

2.8.0 (2025-05-01)

• Add RestClient.device() and RealtimeClient.device() methods which return the LocalDevice object for push notifications #2020
• Add LocalDevice.channelSubscriptions() method which uses device auth to get channel subscriptions only for the local device #2013

2.7.0 (2025-04-17)

• Adds ANNOTATION_PUBLISH and ANNOTATION_SUBSCRIBE channel modes #1953
• Adds support for message annotations via channel.annotations #1953
• The message action meta.occupancy is now renamed to meta. Similarly, MessageActions.META_OCCUPANCY is now MessageActions.META #1953
• Fixes a bug where deactivate would not use device auth, meaning clients would only be able to use it with the push-admin capability #2000
• The push deactivate method's callback type is now optional when using TypeScript #2000

2.6.5 (2025-03-24)

• Fixed type issue in PublishOptions #1988

2.6.4 (2025-03-17)

• Adds new capabilities to control the upcoming message operations. #1949
• These include:
  • message-update-any - the ability to edit a message created by any client on a given channel.
  • message-update-own - the ability to edit only the messages created by the requesting client on a given channel.
  • message-delete-any - the ability to delete a message created by any client on a given channel.
  • message-delete-own - the ability to delete only the messages created by the requesting client on a given channel.

This contains only the most important and/or user-facing changes; for a full changelog, see the commit history.

2.6.3 (2025-01-28)

• Fixed useChannel hook can throw exception in the effect if connection is closed #1938
• Fixed web FetchRequest does not respect disableConnectivityCheck client option #1925
• Fixed typings for RealtimeChannel.modes #1955

2.6.2 (2025-01-14)

• Minor bugfix for experimental message fields.

2.6.1 (2025-01-13)

• Removed an incorrect channel mode ATTACH_RESUME from the ChannelModes enum.
• Removed the UNSET type from MESSAGE_ACTIONS enum, all messages will always have their action set.
• Removed ANNOTATION_CREATE and ANNOTATION_DELETE from the MESSAGE_ACTIONS enum.
• Adds support for upcoming message summaries with the new MESSAGE_SUMMARY message action type.
• Multiple improvements to type definitions and message handling.