npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@assistant-ui/react-lexical

v0.2.24

Published

Lexical-based rich text composer for assistant-ui with @-mention support

Readme

@assistant-ui/react-lexical

Lexical rich-text composer for @assistant-ui/react, with first-class support for @-mention directive chips. Drop LexicalComposerInput in place of the default plain-text composer to render mentions and slash commands as inline chips while keeping the underlying message format clean.

Installation

npm install @assistant-ui/react @assistant-ui/react-lexical lexical @lexical/react @lexical/utils @lexical/history @lexical/plain-text

lexical and the @lexical/* packages this package imports are peer dependencies: your app owns the single Lexical copy that the composer and your own plugins share, so keep every Lexical package at one version.

Usage

import { ComposerPrimitive } from "@assistant-ui/react";
import { LexicalComposerInput } from "@assistant-ui/react-lexical";

export function Composer() {
  return (
    <ComposerPrimitive.Root>
      <LexicalComposerInput aria-label="Message" placeholder="Ask anything..." />
      <ComposerPrimitive.Send />
    </ComposerPrimitive.Root>
  );
}

Use aria-label or aria-labelledby to name the editable textbox (without either, the placeholder names it), and aria-describedby to reference hint or error text. Other HTML props and the forwarded ref apply to the outer wrapper.

For custom chip rendering, pass a directiveChip render prop. Directives (e.g. @user, /command) survive cursor navigation, selection, and copy/paste as a single unit.

Pass custom Lexical plugin components as children to hook into the editor via useLexicalComposerContext, for concerns like paste normalization or length limits.

See also

  • @assistant-ui/react-hook-form for binding the composer to a form whose fields the assistant can read and fill.

Full reference at assistant-ui.com/docs.