Changelog

@liveblocks/node

• WebhookHandler now handles RoomCreatedEvent and RoomDeletedEvent

@liveblocks/client

• Allow createClient throttle option to go as low as 16ms.

@liveblocks/client

• Adds a WebhookHandler class
  • new WebhookHandler(secret).verifyRequest({ rawBody, headers }) can be used to verify event requests from Liveblock's webhook functionality. It also provides fully typed WebhookEvents.
  • Check out our Webhooks guide for more details

• Fixes a bug where history didn't reliably undo LiveObject key set changes if any pending local changes existed on that key.
• Fixes a bug where changes performed inside room.batch were incorrectly ordered inside the history resulting in unexpected undo behavior in some cases.
• Fixes a bug where under some circumstances the Liveblocks client could get stuck in a "synchronizing" state indefinitely
• Expose JsonArray and JsonScalar types publicly

Fix nested storage event handling issue.

Support authentication with cookies.

Export the StorageStatus type (introduced with 0.19.3).

Fix CORS issue.

In @liveblocks/client:

Room.getStorageStatus

Get the storage status.

• not-loaded: Initial state when entering the room.
• loading: Once the storage has been requested via room.getStorage().
• synchronizing: When some local updates have not been acknowledged by Liveblocks servers.
• synchronized: Storage is in sync with Liveblocks servers.

Room.subscribe("storage-status", status => )

Subscribe to storage status changes.

Returns an unsubscribe function.

room.subscribe("storage-status", (status) => {  switch (status) {    case "not-loaded":      break;    case "loading":      break;    case "synchronizing":      break;    case "synchronized":      break;    default:      break;  }});

Room.reconnect

Close the room connection and try to reconnect.

Internal changes

• Add support for the upcoming Liveblocks browser extension

Fixes some internal type definitions.