Changelog

  • Week 46
    WEEK46

    v2.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:

    • In React: <LiveblocksProvider preventUnsavedChanges />

    • Otherwise: createClient({ preventUnsavedChanges: true })

    • Add new API client.getSyncStatus() method.

    • Add new client config option: preventUnsavedChanges.

    • Expose ToImmutable<T> helper type.

    • Add new hook 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 }).

    • Add new LiveblocksProvider prop: preventUnsavedChanges.

    • Deprecated APIs:

      • useStorageStatus is now deprecated in favor of useSyncStatus.

    • Take composers into account when the new preventUnsavedChanges option is set.

    • Add new hook useIsEditorReady which can be used to show a skeleton UI before the editor has received the initial text from the server.

    • Deprecated APIs:

      • useEditorStatus is now deprecated in favor of useIsEditorReady (or useSyncStatus).

    Examples

    Dashboard

    • Redirect users to a specific error page on authentication failure.

    Contributors

    Contributors include:ctnicholasnviemarcbouchenoirenimeshnayajusugardarius

    5 authors

  • Week 45
    WEEK45

    v2.11.0

    • Upgrade dependencies.

    • Fix minor appearance issues related to attachments.

    • Fix pasting issues introduced in 2.10.0.

    • Fix regression with useThreads that caused the hook to return an error if its associated room did not exist.

    • Initial release.

    • Initial release.

    Documentation

    Examples

    Contributors

    Contributors include:sugardariusnimeshnayajumarcbouchenoirejrownyctnicholas

    5 authors

  • Week 44
    WEEK44

    v2.10.2

    • Internal refactorings and code cleanup across various parts of the client's inner workings.

    • Implement automatic retry for initial load of inbox notifications, user threads, room threads, room versions, or room notification settings—except when encountering a 4xx error.

    • Background tabs will no longer poll threads, notification, room versions or room notification settings.

    • Fix incorrect suspense export for useRoomNotificationSettings hook.

    • Support for React 19 and Next.js 15.

    • Support for React 19 and Next.js 15.

    • Support for React 19 and Next.js 15.

    Dashboard

    • Icons indicating which rooms are public/private on room listing and detail pages.
    • New warning message if all your rooms are publicly accessible.

    Documentation

    • Improved clarity on Notifications being project-based.
    • Typo fixes.

    Contributors

    Contributors include:haydenbleaselctnicholaspierrelevaillantnvienimeshnayaju

    5 authors

  • Week 43
    WEEK43

    v2.10.0

    • Add new resolver methods under client.resolvers.* to invalidate the cache of resolveUsers, resolveRoomsInfo, and resolveMentionSuggestions.

    • When subscribing to Storage update events using room.subscribe(root, ..., { isDeep: true }), all LiveList deletion updates will now also include the item that was deleted.

    • Improve and fix pasting rich text into the composer.

    • Improve mention suggestions click behavior.

    Dashboard

    • Removed Show deleted threads checkbox from the room detail Comments tab to ensure consistent behavior across dashboard and APIs.

    Documentation

    • Prevent truncated API keys being copied in code snippets.
    • Typo fixes.

    Contributors

    Contributors include:pierrelevaillantsugardariuskaf-lamed-beytctnicholasmarcbouchenoirenvie

    6 authors

  • Week 42
    WEEK42

    v2.9.1

    • Fix regression with metadata filtering on explicitly-undefined values.

    • Fix bug where client wasn't always using the newest delta update backend endpoint yet.

    • Fix type definition of ThreadData: updatedAt is always set.

    • When Composer is disabled, its actions are now also disabled as expected.

    • Various event propagation improvements in Composer.

    v2.9.0

    We are introducing pagination support to allow apps using threads and inbox notifications to be built in a more user-friendly way, where the initial load is faster and more data can be fetched incrementally as users interact with the app.

    • Add pagination support to useInboxNotifications.

      const {  inboxNotifications,  isLoading,  error,
        // ✨ New in Liveblocks 2.9  fetchMore,  isFetchingMore,  hasFetchedAll,  fetchMoreError,} = useInboxNotifications();

    • Add pagination support to useThreads and useUserThreads_experimental.

      const {  threads,  isLoading,  error,
        // ✨ New in Liveblocks 2.9  fetchMore,  isFetchingMore,  hasFetchedAll,  fetchMoreError,} = useThreads({ query });

    Website

    • New startups page highlighting discounts for startups and nonprofits.

    Contributors

    Contributors include:nimeshnayajuofoucherotmarcbouchenoirenviepierrelevaillantstevenfabre

    6 authors

  • Week 40
    WEEK40

    v2.8.2

    • Send client version in HTTP request headers from the client, to ensure backward compatible responses from the server

    v2.8.1

    • Expose onComposerSubmit on Thread to react to the inner composer of a thread.

    Website

    • Refresh pricing page design

    Dashboard

    • Add attachments support to the comments view on the room detail page

    Figma Kit

    Contributors

    Contributors include:marcbouchenoiresugardariuspierrelevaillantnvie

    4 authors

  • Week 39
    WEEK39

    v2.8.0

    We are introducing attachments to allow users to add files to their comments, for more information about this change please read our Upgrade Guide for 2.8.

    • Add out-of-the-box support for attachments in the default components.

    • Add new primitives to support attachments in custom components:

      • Composer.AttachmentsDropArea: Receives files via drag-and-drop
      • Composer.AttachFiles: Opens a file picker
      • FileSize: Displays a formatted file size

    • Add values and methods to useComposer to support attachments in custom components.

    • Add useAttachmentUrl hook to get presigned URLs for attachments.

    • Add prepareAttachment and uploadAttachment methods to Room to create attachments.

    • Add getAttachmentUrl method to Room to get presigned URLs for attachments.

    Website

    • New blog post: Next.js Template Week recap.
    • Bug fix on the pricing page MAU slider which didn't apply the MAU value set to the price of the products.

    Contributors

    Contributors include:ctnicholasstevenfabremarcbouchenoireofoucherotflowflorent

    5 authors

  • Week 38
    WEEK38

    v2.7.2

    • Fix a bug where under some conditions threads could end up without comments.
    • Fix a bug where notifications associated to deleted threads would not be deleted.
    • Fix a bug where subsequent optimistic updates to the same inbox notification could sometimes not get applied correctly.

    v2.7.1

    • Fixed a bug where resolved threads remained visible in the editor and the AnchoredThreads and FloatingThreads components.

    Examples

    Documentation

    Dashboard

    • Fix a bug where room storage data wasn't fetched correctly and not displayed in the room detail storage tab.
    • Fix a bug where room storage data couldn't be deleted from the room detail storage tab.

    Contributors

    Contributors include:ctnicholasnimeshnayajumarcbouchenoirenviesugardarius

    5 authors

  • Week 37
    WEEK37

    v2.7.0

    • Refactor caching internals to prepare for upcoming features.

    • Add support for query argument to useUserThreads_experimental.

    • Fix bug where some combinations of query criteria could over-select threads in useThreads.

    2.6.1

    • Fix mention suggestions dropdown not following scroll in some scenarios.

    Dashboard

    • Improved error messages to provide clearer guidance during team creation.
    • Implemented various bug fixes and performed stabilization work to enhance overall system reliability.

    Contributors

    Contributors include:nvieflowflorentjrownymarcbouchenoiresugardariusnimeshnayaju

    6 authors

  • Week 36
    WEEK36

    Website

    Documentation

    Contributors

    Contributors include:ctnicholas

    1 authors

We use cookies to collect data to improve your experience on our site. Read our Privacy Policy to learn more.