Lextrix — TypeScript rich-text editor

Modular by design

Use the published lextrix bundle or compose lextrix-core, lextrix-dom, lextrix-formats, lextrix-modules, lextrix-serialize, and lextrix-ui for custom builds.

Official React bindings

@lextrix/react ships LextrixEditor — controlled Markdown/HTML/MDX, destroy on unmount, and 'use client' for Next.js App Router.

Native serialization

importContent / exportContent for HTML, Markdown, MDX, and JSON — all routed through ChangeSet via lextrix-serialize.

Predictable change pipeline

ChangeSets with compose, diff, transform, and invert — used for undo/redo and future collaboration work.

Framework agnostic

Vanilla class API for any framework; React apps should use @lextrix/react. Vue and others mount with destroy() on teardown.

Extensible registry

Register formats, modules, serializers, and themes via lxr/* paths without modifying editor internals.

Full editor ESM + UMD + CSS — npm install lextrix

LextrixEditor component — peer depends on lextrix ^2.0.5

ChangeSet layer and operational transform utilities

Blots, attributors, registry, and DOM sync

Selection, commands, plugin host, and editor lifecycle

Bold, lists, headers, links, code blocks, tables, embeds

Clipboard, keyboard, toolbar, syntax, image resize, tables

Headless Markdown, MDX, JSON ↔ ChangeSet import/export

Toolbar widgets and icons for Lextrix UI integrations

Snow, Bubble, Slate, and Dawn theme styles

Why I Started Building Lextrix

The origin story — wrong monoliths, package splits, and why the editor exists.

What Reading Quill's Source Code Taught Me About Editors

Deltas, blots, clipboard, and the mental model that led to Lextrix.

Lessons Learned Building a TypeScript Library

npm publishing lessons from lextrix and sudoku-engine.