lextrix

Lextrix

Version 3.0.0 — a programmable document engine with a rich-text editor projection.

Built by Reetesh Kumar · Playground · Docs · Repo docs

Lextrix is more than a WYSIWYG editor. ChangeSets are the canonical transitions; Documents and Versions are immutable state; the browser editor projects that state. Collaboration, persistence, and intelligence plug in through stable ports — without putting Auth, billing, or LLM vendors inside the core engine.

What you get

Invariants: DocumentState ≠ ChangeSet · History ≠ Versioning · AI never directly mutates · Server owns Version IDs · ADR-012 wire schemaVersion: 1.

Quick start (editor)

npm install lextrix

import Lextrix from 'lextrix';
import 'lextrix/snow.css';

const editor = new Lextrix('#editor', {
  theme: 'snow',
  modules: { toolbar: [['bold', 'italic'], ['link']] },
});

React: npm install lextrix @lextrix/react — see React guide.

Document engine (stable imports)

import ChangeSet from 'lextrix-change';
import { DocumentHandle } from 'lextrix-change/document';
import { parseChangeSet } from 'lextrix-change/wire';

Details: API stability.

Playground

Local platform demo (editor + Document/Version/Proposal/collab/infra panels):

npm run demo
# → http://localhost:5173

Guide: docs/playground.md. Uses real package APIs. Collaboration/persistence panels are in-memory reference demos — not a claim of live PostgreSQL or production WebSocket.

Playwright tests: npm test -w lextrix-demo (builds via Vite).

Develop / test / build

npm install
npm run build
npm test                 # engine + Chromium unit suites
npm run test:unit -w lextrix
npm run test:e2e -w lextrix
npm run typecheck

Packages

Architecture & validation

• Documentation site · Repo docs
• Architecture overview
• ADRs
• Final system validation
• Future roadmap (discovery — not a build commitment)
• Changelog
• Migrate from 2.1

Current limitations (honest)

Release-ready for implemented scope, with documented limits:

• Live PostgreSQL / multi-process fencing / WS soak / numeric SLOs may be environment-gated
• Presence protocol exists; presence UX is deferred
• Automated multi-region product, SaaS/billing, CRDT, E2EE are not claimed
• See validation report for the full scorecard

License

MIT