Changelog

@liveblocks/client

• Fix a bug where calculating the insertion position between two existing elements could happen incorrectly in a small edge case

@liveblocks/*

• #1177 Fix an issue with internal LiveList serialization that could lead to a "ghosting" bug with @liveblocks/zustand / @liveblocks/redux when using tuples.

@liveblocks/node

• Add comment reaction webhook events CommentReactionAdded and CommentReactionRemoved

DevTools

• New Yjs tab: visualize Yjs documents as a diagram, a tree, or as a list of operations, and inspect Awareness at the same time as Presence.
• New Events tab: inspect all custom Events a client receives in an event timeline, for easy testing/debugging.

@liveblocks/yjs

• Add support for the Liveblocks DevTools.

@liveblocks/client

• Broadcast event messages now include a user property to indicate the user that sent the event:

  room.subscribe("event", ({ event, user }) => {  //                              ^^^^ New!});

@liveblocks/react

• Broadcast event messages now include a user property to indicate the user that sent the event:

  useEventListener(({ event, user }) => {  //                       ^^^^ New!});
• Breaking (beta): Comments' hook useThreads now returns an object in its Suspense version. (const threads = useThreads() becomes const { threads } = useThreads())

@liveblocks/react-comments

• Breaking (beta): Comment’s indentBody and Thread’s indentCommentBody were renamed to indentContent and indentCommentContent respectively. Thread’s onResolveChange was renamed to onResolvedChange.
• Add emoji button in Composer.

@liveblocks/node

• Support using @liveblocks/node in Edge runtimes.

@liveblocks/client

• Support unstable_fallbackToHTTP client option when using any auth token type (previously it only worked when using single-room tokens, which we no longer recommend since 1.2)

@liveblocks/react

• Officially mark useList(), useMap(), and useObject() as deprecated in JSDoc comments (we stopped recommending them since the release of 0.18)
• Deduplicate Comments requests and improve how race conditions are handled during mutations.
• Fix non-Suspense Comments hooks not working properly in some situations.

@liveblocks/react-comments

• Breaking (beta): Replace the render prop API (e.g. renderMention, renderLink, etc) by a single components prop. (e.g. components={{ Mention, Link }})
• Fix overflowing Composer.Suggestions.
• Reduce the impact of icons on bundle size.

@liveblocks/react

• Fix confusing Error: "undefined" is not a valid event name error when using the (deprecated) useMap(), useObject(), or useList() hooks on uninitialized storage values.

@liveblocks/*

• Fix unescaped room IDs when using Comments.

@liveblocks/react-comments

• Add support for auto links. (e.g. "www.liveblocks.io")

@liveblocks/client

• The client will disconnect with an error if your /api/liveblocks-auth backend returns reused/cached tokens. It’s important that auth tokens are always freshly generated, and never get cached or reused. (The client itself will cache and reuse tokens already, so implementing additional caching in your backend isn’t needed, and could even cause reconnection issues.)

@liveblocks/client

• Actually include the new Clear History API.

@liveblocks/react

• Fix missing dependency declaration.

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.