Changelog

This release marks the initial release of Liveblocks Comments (private beta).

@liveblocks/client

• New history API: room.history.clear() allows you to explicitly clear the history, which resets the ability to undo beyond the current state.
• Removed long deprecated methods:
  • others.count → Use others.length instead
  • others.toArray() → Use others instead (it’s already an array)
• Deprecated the Others<P, U> type → Use readonly User<P, U>[] instead.

@liveblocks/react

• Add support for Comments.
• UserMeta["info"] can no longer be a scalar value.

@liveblocks/react-comments

• Initial release.

@liveblocks/node

• Add Comments helpers to Client.
• Add Comments webhook events.

@liveblocks/node

• Fixes a bug where sending an empty (or non-string) user ID with .identifyUser would confusingly get reported as an HTTP 503.

@liveblocks/client

• Improve configuration error messages to be more user friendly.
• Fix bug where entering a new room could potentially initialize the undo stack incorrectly.

create-liveblocks-app

• Fix Suspense option when specifying a framework.
• Add helpful comments by default.

@liveblocks/node

• Add Yjs document change event (YDocUpdatedEvent) to WebhookHandler.
• Allow Header object to be passed to headers in WebhookHandler.verifyRequest()

@liveblocks/node

• Fix session.allow to support path up to 128 characters to meet room id length requirement.

@liveblocks/*

• Support the new and improved Liveblocks authorization.
• Change client logic to stop retrying if room is full. Instead, the client will now disconnect. To retry, call room.reconnect() explicitly.

@liveblocks/node

• Add new APIs for authorization. See our migration guide for tips on how to adopt the new style of authorizing your Liveblocks clients.

• Fix a small TypeScript issue introduced in 1.1.7.

@liveblocks/client

• When initializing the client with a custom auth callback, you can now return { error: "forbidden", reason: ... } as the response, which the client will treat as a sign to stop retrying. The client will then disconnect from the room, instead of remaining in "connecting" status indefinitely.

@liveblocks/react

• Fix a bug with useSelf() where it would not correctly re-render after entering an empty room. It’s now consistent again with useMyPresence().

DevTools

• Fix a bug in the Liveblocks DevTools panel where the "me" view would incorrectly stay empty after entering an empty room.

@liveblocks/*

• Loosen duplicate import detection so it won't throw when used in test runners that deliberately run multiple instances of a module (like Jest or Playwright can do).

@liveblocks/*

• Ship all of our packages as both ESM and CJS modules again (restore the changes that 1.1.3 originally introduced).
• Auto-detect if multiple copies of Liveblocks are included in your production bundle. If so, a help page is presented that will help you resolve this issue.
• Fix a bug where the room internals could become non-functional when used in combination with Immer due to Immer’s excessive auto-freezing, which would break the room’s internals. (This became an issue since Liveblocks 1.1 was released.)