Security News
cURL Project and Go Security Teams Reject CVSS as Broken
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
@liveblocks/node-lexical
Advanced tools
A server-side utility that lets you modify lexical documents hosted in Liveblocks.
@liveblocks/node-lexical
Licensed under the Apache License 2.0, Copyright © 2021-present Liveblocks.
See LICENSE for more information.
v2.16.0
Our error listener APIs will now receive more errors in general, including errors from using Comments & Notifications. Previously, these would only receive room connection errors from Presence, Storage, or Yjs.
For example, now when creation of a thread fails, deletion of a comment fails, marking a notification as read fails, etc.
@liveblocks/react
useErrorListener()
// ❌ Before: required a RoomProvider and would only notify about errors for that room
// ✅ Now: requires a LiveblocksProvider and will notify about errors for any room
useErrorListener((err: LiveblocksError) => {
/* show toast, or notify Sentry, Datadog, etc */
});
See the Upgrade Guide for 2.16 to learn how to adapt your code.
We now support filtering threads by absence of metadata as well in
useThreads({ query })
(or useUserThreads_experimental({ query })
).
For example, you can now filter threads that do not have a color
attribute set
in their metadata:
useThreads({
query: {
// Filter any "pinned" threads that don't have a color set
metadata: {
pinned: true,
color: null, // ✨
},
},
});
See the Upgrade Guide for 2.16 to learn how to adapt your code.
@liveblocks/client
The error listener APIs will now receive more errors in general, including errors from using Comments & Notifications. Previously, these would only receive room connection errors from Presence, Storage, or Yjs.
// 👌 Same as before, but might now also receive errors related to Comments & Notifications
room.subscribe("error", (err) => { ... });
@liveblocks/react-ui
<Icon.* />
via import { Icon } from "@liveblocks/react-ui"
.@liveblocks/react-lexical
and @liveblocks/react-tiptap
<Toolbar />
and <FloatingToolbar />
components to simplify building
editor toolbars. They come with default controls out-of-the-box based on what
the editor they’re attached to supports, but they’re also heavily extendable
and customizable. Use inner components like <Toolbar.Toggle />
and
<Toolbar.Separator />
to extend the defaults with your own actions, or start
from scratch while customizing some of the defaults via
<Toolbar.SectionInline />
or <Toolbar.BlockSelector />
for example.@liveblocks/react-lexical
isTextFormatActive
and isBlockNodeActive
utilities.@liveblocks/yjs
useV2Encoding_experimental
to LiveblocksYjsProvider
to
enable experimental V2 encoding for Yjs.FAQs
A server-side utility that lets you modify lexical documents hosted in Liveblocks.
The npm package @liveblocks/node-lexical receives a total of 545 weekly downloads. As such, @liveblocks/node-lexical popularity was classified as not popular.
We found that @liveblocks/node-lexical demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.
Security News
Biden's executive order pushes for AI-driven cybersecurity, software supply chain transparency, and stronger protections for federal and open source systems.