Lextrix — Document engine and rich-text editor

Editor still ships

Mount themes, formats, and modules as before. The browser editor is the projection layer — not a discarded prototype.

Document engine underneath

Document, DocumentHandle, Versions, Anchors, Ranges, and ChangeProposals live in lextrix-change for history, sync, and review.

Official React bindings

@lextrix/react 0.3.0 ships LextrixEditor — controlled Markdown/HTML/MDX, destroy on unmount, peer lextrix ^3.0.0.

OT collaboration

ChangeSet transform/rebase with an authoritative server — not CRDT. Clients submit ChangeSets; the server owns Version identity.

Durable persistence ports

compareAndAppend CAS, changeId idempotency, and owner_epoch fencing — with a PostgreSQL + WebSocket reference host.

AI as proposals only

lextrix-intelligence produces ChangeProposals. Explicit accept — never privileged Document or Editor mutation.

Full editor ESM + UMD + CSS — npm install lextrix@3.0.0

LextrixEditor component — peer depends on lextrix ^3.0.0

ChangeSet OT, Document runtime, wire, persistence/collab ports

Authoritative sessions, envelopes, reconnect, presence protocol

PostgreSQL persistence + WebSocket collab server

Deterministic / OpenAI providers — proposals only

Blots, attributors, registry, and DOM sync

Selection, PluginHost, and EditorDocumentBridge

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. Historical relative to 3.0.0.

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.