@liveblocks/yjs
Advanced tools
Changelog
2.12.2 (Not published yet)
@liveblocks/zustand
Changelog
2.12.0
This release adds support for tracking synchronization status of pending local changes for any part of Liveblocks. Whether you use Storage, Text Editors, Threads, or Notifications.
If the client’s sync status is synchronized
, it means all local pending
changes have been persisted by our servers. If there are pending local changes
in any part of Liveblocks you’re using, then the client’s sync status will be
synchronizing
.
Also, we’re introducing a way to prevent browser tabs from being closed while
local changes are not yet synchronized. To opt-in to this protection, enable
preventUnsavedChanges
option on the client:
<LiveblocksProvider preventUnsavedChanges />
createClient({ preventUnsavedChanges: true })
@liveblocks/client
client.getSyncStatus()
method.preventUnsavedChanges
.ToImmutable<T>
helper type.@liveblocks/react
useSyncStatus
that can be used to tell whether Liveblocks is synchronizing local changes to
the server. Useful to display a "Saving..." spinner in your application, when
used with useSyncStatus({ smooth: true })
.useStorageStatus
is now deprecated in favor of useSyncStatus
.@liveblocks/react-ui
preventUnsavedChanges
option is
set.@liveblocks/react-lexical
useIsEditorReady
which can be used to show a skeleton UI before
the editor has received the initial text from the server.useEditorStatus
is now deprecated in favor of useIsEditorReady
(or
useSyncStatus
).Changelog
2.11.1
@liveblocks/react-lexical
AnchoredThreads
component not working correctly on certain
React versions.@liveblocks/react-tiptap
AnchoredThreads
component not working correctly on certain
React versions.shouldRerenderOnTransaction: false
is set.@liveblocks/yjs
LiveblocksYjsProvider
.Changelog
2.11.0
@liveblocks/react-ui
@liveblocks/react
useThreads
that caused the hook to return an error if
its associated room did not exist.@liveblocks/react-tiptap
@liveblocks/emails