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

extendable-lexical-editor

v1.4.1

Published

A custom fork of '@lexical/monorepo' internal package 'lexical-playground'.

Readme

Purpose

This library provides an extendable, production-ready wrapper around the Lexical playground: a reusable <ExtendableEditor /> React component plus a curated set of nodes, themes, contexts, and plugins. It’s intended to be a starting point for building rich-text editors that you can customize with your own nodes, toolbar, and behaviors.

How to set up and use <ExtendableEditor />

Here’s a minimal example for an external app that installed this package. Install and then import from the exported subpaths:

npm install extendable-lexical-editor react react-dom

Then use the component:

'use client';

import {useState} from 'react';

import nodes from 'extendable-lexical-editor/editor-nodes';
import theme from 'extendable-lexical-editor/editor-theme';
import ExtendableEditor from 'extendable-lexical-editor/extendable-editor';

import 'extendable-lexical-editor/extendable-editor.css';

export default function RichTextEditor() {
  const [document, setDoc] = useState(null);

  return (
    <ExtendableEditor
      collabDocId="collaboration-TnnMG5W8MA" // identifier for collaboration room
      name="rich-text-editor"                // editor name (for diagnostics)
      namespace="app-name"                   // editor namespace (for serialization/source)
      nodes={nodes}                          // optional: extend with your own nodes
      theme={theme}                          // optional: customize styling
      initialDocument={document ?? undefined}
      onChangeDocument={setDoc}
      onSaveDocument={(document) => {
        // Invoked on Cmd/Ctrl+S (handled internally)
        console.log('Saved document:', document);
      }}
    />
  );
}

Notes:

  • The component merges your features with sensible defaults; pass a partial config via the features prop only if you need overrides.
  • Use onChangeDocument to keep external state in sync, and onSaveDocument to persist via Cmd/Ctrl+S.
  • You can provide your own nodes array and theme to fully customize behavior and appearance.

Using the serialized schema (Lexical JSON)

  • For building strongly-typed editorState JSON, see the standalone schema in types/LexicalSchema.d.ts.
  • Usage guide: types/README.md
  • Import path for consumers: extendable-lexical-editor/lexical-schema