We’ve introduced first-party support for BlockNote text editor, new APIs for mutating realtime Storage and rooms on the server, new configuration options for external user notifications, and we’re now SOC2 Type 2 and HIPAA compliant.
Join thousands of companies using Liveblocks ready‑made collaborative features to drive growth in their products.
This March we’ve released APIs for various features, and committed to security.
To use the latest features, update your packages with the following command.
If you were previously on Liveblocks 2.15 or below, make sure to follow our upgrade guides before updating.
It’s now easier than ever to add a collaborative block-based text editor to your app, filled with features out-of-the-box. Liveblocks BlockNote is our new fully-hosted customizable editor, which integrates into our existing products, such as Comments and Notifications.
To learn more, and to find our new examples and guides, make sure to read our focused blog post on Notion-style collaborative editing with BlockNote.
Our Sync Datastore product provides you with two sync engines that enable storing real-time document state, ideal for building collaborative apps. One of these engines is called Storage, and is particularly well suited for creating custom tools similar to Figma, Pitch, and Spline.
Using our Node.js SDK, you can now modify
Storage data from the server with
mutateStorage.
This is particularly exciting in the AI era, as you can request AI to make changes to your document for your user. Below is how you may implement this with Vercel AI SDK, generating a title from an article’s content.
We’ve also added another method, that allows you to modify Storage in multiple rooms at once. This is particularly useful for migrating rooms to a new schema, or for resetting a number of rooms at once. Below we’re setting a default title property in every room.
You can also use options to filter for specific rooms, learn more under
massMutateStorage.
Below we’re setting a title property, in realtime.
Liveblocks Notifications already allows you to create an in-app notifications inbox inside your product. When users miss any in-app notifications, Liveblocks enables sending notifications on alternate channels, such as email, Slack, Microsoft Teams, Web Push.
As of this month, we’ve introduced new configuration options that enable building notification settings panels, allowing each of your end users to individually choose which channels they should receive notifications on.
To learn more, and to find our new examples and guides, make sure to read our focused blog post on configuring each user’s notification settings for email, Slack, and more.
We’ve added a number of new methods to the Liveblocks Node.js SDK, simplifying
regular use cases. For example,
getOrCreateRoom
combines getRoom and createRoom into a single method.
Learn more about each new method in our API reference:
At Liveblocks, security and privacy have always been top priorities. We understand that as companies integrate collaboration and AI-powered features into their products, they need to trust that their data remains secure and compliant with industry standards. In March, we announced that Liveblocks is now SOC 2 Type 2 and HIPAA compliant, reinforcing our commitment in this area.
Learn more about the certification process and how we acheived compliance in our blog post about our SOC 2 Type 2 and HIPAA commitments.
Here’s a list of other improvements in our changelog this month:
.getOrCreateRoom() and .upsertRoom() to only make a single
round-trip to the server.LiveObject, LiveMap, and LiveList in @liveblocks/node..getInboxNotifications().<Icon.* />.AbortSignal to all Node.js methods.deleteRoom to no
longer throw when the room already does not exist.v2.18.3 when we added support for whitespace within mentions.Composer.useRoom({ allowOutsideRoom: true }) option. When this option is
set, the hook will return null when used outside of a room, whereas the
default behavior of the hook is be to throw.UserNotificationSettings object to return
null to prevent any errors when accessing a disabled notification channel.@liveblocks/react-blocknote.markThreadAsResolved and markThreadAsUnresolved methods not passing
user ID correctly to the corresponding backend endpoints.To use these latest features, update your packages with:
Contributors include:
8 authors