Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@liveblocks/client

Package Overview
Dependencies
Maintainers
0
Versions
427
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@liveblocks/client - npm Package Versions

13
43

2.13.1-emails1

Diff

liveblocks-bot
published 2.13.0 •

Changelog

Source

2.13.0

@liveblocks/react-ui

  • Add a formatting toolbar to Composer which appears when selecting text. It’s enabled by default in the default components and can also be custom built with new primitives (Composer.FloatingToolbar and Composer.MarkToggle) and new APIs (const { marks, toggleMark } = useComposer()).
  • Add new --lb-line-height token to control the line height of main elements (e.g. comment bodies in comments and composers).
  • Remove Timestamp export mistakenly added to @liveblocks/react-ui, it should be imported from @liveblocks/react-ui/primitives instead.
liveblocks-bot
published 2.12.3-emails1 •

liveblocks-bot
published 2.12.2 •

Changelog

Source

2.12.2

@liveblocks/react-tiptap

  • Add new options for useLiveblocksExtension() to allow setting initialContent, experimental offline support, and the field name
  • Update floating composer to support onComposerSubmit handler and closing the composer with the escape key

@liveblocks/zustand

  • Add support for Zustand v5
liveblocks-bot
published 2.12.1-test3 •

guillaumesalles
published 2.12.1-test2 •

guillaumesalles
published 2.12.1 •

Changelog

Source

2.12.1

@liveblocks/react-ui

  • Prevent unsupported attachment previews from loading infinitely.
  • Refactored Thread and Comment component to be used outside of the RoomProvider component.
guillaumesalles
published 2.12.1-emails1 •

guillaumesalles
published 2.12.1-test1 •

guillaumesalles
published 2.12.0 •

Changelog

Source

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:

  • In React: <LiveblocksProvider preventUnsavedChanges />
  • Otherwise: createClient({ preventUnsavedChanges: true })

@liveblocks/client

  • Add new API client.getSyncStatus() method.
  • Add new client config option: preventUnsavedChanges.
  • Expose ToImmutable<T> helper type.

@liveblocks/react

  • 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 }).
  • Deprecated APIs:
    • useStorageStatus is now deprecated in favor of useSyncStatus.

@liveblocks/react-ui

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

@liveblocks/react-lexical

  • 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).
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc