@liveblocks/yjs
Advanced tools
Changelog
v1.11.3
@liveblocks/client
RangeError: Maximum call stack size exceeded
in
applications that produce many operations@liveblocks/node
updatedAt
property to YDocUpdatedEvent
type.
(@alexlande)Changelog
v1.11.2
create-liveblocks-app
Changelog
v1.11.1
@liveblocks/react-comments
@liveblocks/node
process
is undefined" issue in Vite builds. This issue was already
fixed for @liveblocks/client
, but not for @liveblocks/node
yet.Changelog
v1.11.0
@liveblocks/node
updateRoomId
method that lets you update the room ID of the specified
room.guid
parameter to sendYjsBinaryUpdate
and
getYjsDocumentAsBinaryUpdate
to point to a Yjs subdocument with the
specified guid.@liveblocks/react
scrollOnLoad
option to useThreads
: enabled by default, this option
controls whether to scroll to a comment on load based on the URL hash.useUser
and useRoomInfo
no longer support returning nothing. Returning
undefined
will now be treated as an error.useUser
and useRoomInfo
returned an extra data
superfluous
property.createLiveblocksContext
would conflict
with the provided Client
.@liveblocks/react-comments
InboxNotification
with a single action for now: marking as
read.Comment
/Thread
.Comment
background color when it’s linked to or being edited.Changelog
v1.10.4
process is not defined
could
happenChangelog
v1.10.3
@liveblocks/react-comments
bn
) and Hindi (hi
).showRoomName
prop on InboxNotification.Thread
wasn’t
applied to notifications about mentions.@liveblocks/react
useEditThreadMetadata
would result in a
brief flash of the old metadata after the metadata was removed optimistically.Changelog
v1.10.2
@liveblocks/client
.clone()
immediately after creating a new LiveObject
could throw an errorChangelog
v1.10.1
@liveblocks/client
@liveblocks/react-comments
InboxNotification
.@liveblocks/react
useThreads
, useRoomNotificationSettings
, and
useInboxNotifications
during initial fetching.