@flyos/design-system-editor

The FlyOS design system's rich-text editing surface: fly-markdown-editor, fly-chat-composer, fly-symbol-picker, the Tiptap extensions they are built on (authorized image, FlyOS link, math inline/block, chat mention + emoji nodes, emoji shortcuts, symbol catalog) and the bilingual markdown field.

It peer-depends on @flyos/design-system and consumes it as an ordinary bare package import — pipes, services, models and the emoji catalog all stay in the core library.

Deliberately NOT a federation singleton

This package is not part of the @flyos/design-system bundle and is not registered as a Native Federation shared singleton. It carries the entire Tiptap/KaTeX/linkifyjs stack, and only editor-using apps should pay for it — every other remote gets a core design system with none of it. Consumers import it directly and it is bundled per-consumer, the same posture as @flyos/design-system-twin-face.

Sharing it as a singleton would defeat the split: the shared-singleton contract would force every remote in the shell to load the editor stack whether or not it renders an editor.

Usage

import { FlyMarkdownEditorComponent } from '@flyos/design-system-editor';