Changelog

• Fix bug where passing down shouldInitiallyConnect connection option would not always work.

• Log stack traces of function calls that resulted in rejected storage mutations to the console in non-production builds to ease debugging.

@liveblocks/client

• Fixes bug where the state of others in a room was wrong when:
  • Client A disconnects improperly (ex: computer goes to sleep)
  • Then Client B disconnects (ex: computer goes to sleep)
  • Then Client A reconnects: client B still shows in the others state

This major release marks the maturity of Liveblocks. For upgrade instructions, see the 1.0 upgrade guide.

@liveblocks/node

authorize option userId is now mandatory.

Our new pricing is based on Monthly Active Users instead of connections. We're using userId to track MAU associated to a Liveblocks account.

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