@liveblocks/react-ui

• Improve AiChat's scroll behavior when sending new messages: the chat will now scroll new messages to the top and leave enough space for responses.
• Expose Markdown components in AiChat’s components prop to customize the rendering of Markdown content.
• Add blurOnSubmit prop to Composer (also available on the Composer.Form primitive and as blurComposerOnSubmit on Thread) to control whether a composer should lose focus after being submitted.

@liveblocks/react

• useErrorListener now receives "LARGE_MESSAGE_ERROR" errors when the largeMessageStrategy option isn’t configured and a message couldn’t be sent because it was too large for WebSocket.

@liveblocks/node

• Add tenantId to identifyUser method as an optional parameter.

@liveblocks/react-ui

• Fix copilot id not being passed to set-tool-call-result command that is dispatched when a tool call is responded to. Previously, we were using the default copilot to generate messages from the tool call result.

@liveblocks/react-ui

• Fix AiChat component not scrolling instantly to the bottom on render when
  messages are already loaded.

@liveblocks/react-ui and @liveblocks/emails

• Improve URL sanitization in comments.

@liveblocks/client

• Adds experimental setting LiveObject.detectLargeObjects, which can be
  enabled globally using LiveObject.detectLargeObjects = true (default is
  false). With this setting enabled, calls to LiveObject.set() or
  LiveObject.update() will throw as soon as you add a value that would make
  the total size of the LiveObject exceed the platform limit of 128 kB. The
  benefit is that you get an early error instead of a silent failure, but the
  downside is that this adds significant runtime overhead if your application
  makes many LiveObject mutations.
• Fix: also display errors in production builds when they happen in render
  methods defined with defineAiTool(). Previously, these errors would only be
  shown during development.
• Fix an issue with the render component of tool calls not being displayed
  correctly when the tool call signal was read before it was registered.

@liveblocks/client

• defineAiTool()() now takes an optional enabled property. When set to false, the tool will not be made available to the AI copilot for new/future chat messages, but still allow existing tool invocations to be rendered that are part of the historic chat record.

@liveblocks/react

• RegisterAiTool now also takes an optional enabled prop. This is a convenience prop that can be used to override the tool’s enabled status directly in React.

@liveblocks/react-ui

• Reasoning parts in AiChat are now automatically collapsed when the reasoning is done.
• Add collapsible prop to AiTool to control whether its content can be collapsed/expanded.
• Add InboxNotification.Inspector component to help debugging custom inbox notifications.

@liveblocks/redux

• Add support for Redux v5.

@liveblocks/react-lexical

• Fix default z-index of collaboration cursors, and make them inherit their font family instead of always using Arial.
• Add lb-lexical-cursors class to the collaboration cursors’ container.
• Improve mentions’ serialization.

@liveblocks/node-lexical

• Improve mentions’ serialization.

Liveblocks 3.0 is our third major release, focusing on our newest product, AI Copilots. We’ve used this as an opportunity to tidy up some of our existing APIs, ensuring consistency throughout our offering.

For full upgrade instructions and codemods, see the 3.0 upgrade guide.

All packages

• TypeScript 5.0 is now the minimum supported version.
• Remove deprecated APIs, see the deprecated section in the upgrade guide to learn more.

@liveblocks/react

• Introduce hooks and APIs for AI Copilots: useAiChats, useAiChat, useDeleteAiChat,useSendAiMessage, RegisterAiTool, RegisterAiKnowledge, etc.
• Rename UPDATE_USER_NOTIFICATION_SETTINGS_ERROR to UPDATE_NOTIFICATION_SETTINGS_ERROR when using useNotificationSettings or useUpdateNotificationSettings.

@liveblocks/react-ui

• Introduce pre-built components for AI Copilots: AiChat, AiTool, etc.
• The onMentionClick prop on Thread and Comment now receives a MentionData object instead of a userId string.
• The Mention component on the Comment.Body and Composer.Editor primitives now receives a mention prop instead of a userId one.
• The MentionSuggestions component on the Composer.Editor primitive now receives a mentions prop instead of a userIds one, and the selectedUserId prop has been renamed to selectedMentionId.
• Rename LiveblocksUIConfig to LiveblocksUiConfig for consistency with other Liveblocks APIs.

@liveblocks/emails

• Remove deprecated htmlBody/reactBody properties from prepareThreadNotificationEmailAsHtml/prepareThreadNotificationEmailAsReact, use body instead.
• Remove htmlContent/reactContent properties from prepareTextMentionNotificationEmailAsHtml/prepareTextMentionNotificationEmailAsReact, use content instead.
• The prepareTextMentionNotificationEmailAsReact and prepareTextMentionNotificationEmailAsHtml functions’ returned data changed slightly:
  • The id property is now named textMentionId, it refers to the mention’s Text Mention ID, not the user ID used for the mention
  • The id property now refers to the mention’s ID, as in the user ID used for the mention
• The element prop received by the Mention component in prepareTextMentionNotificationEmailAsReact now contains an id property instead of userId, and a new kind property to indicate the mention’s kind.

@liveblocks/client and @liveblocks/node

• The getMentionedIdsFromCommentBody utility has been replaced by getMentionsFromCommentBody.

@liveblocks/react and @liveblocks/react-ui

• Fix an issue with subpath imports (e.g. @liveblocks/react/suspense) and CommonJS which could happen with certain bundlers.

@liveblocks/react-ui

• Disable or hide actions in Thread and Comment components for users without permission to perform them, such as adding reactions or (un)resolving threads.

v2.24.1

@liveblocks/yjs

• Fix for occasional desync issue