Executable migration guide
Migrate from TinyMCE to RichTextEditor
Map common configuration and transfer real document content with the package adapter, while keeping unsupported features visible for review.
Install and run
import { migrateConfig, migrateEditor } from
"@richscripts/richtexteditor/migration";
const plan = migrateConfig("tinymce", legacyConfig);
const result = migrateEditor("tinymce", legacyEditor, rte);
console.table(result.warnings);Content handoff
editor.getContent() is the source API. HTML passes through to RichTextEditor for its normal sanitization and normalization pipeline.
Configuration result
migrateConfig() returns target config, mapped commands, unmapped items and warnings. Review the report before replacing production initialization.
Automated coverage
- Maps common toolbar tokens, dimensions, placeholder and read-only mode.
- Reads a live instance through getContent().
- Reports custom toolbar items instead of silently discarding them.
Manual review remains
- Premium comments, revision history and track changes need application-data migration.
- Custom plugins, schema rules, templates and content CSS remain application work.
Acceptance checklist
- Run the adapter on repository fixtures and representative production documents.
- Review every warning and unmapped toolbar item.
- Compare saved HTML—not only rendered appearance.
- Rebuild custom commands, uploads, permissions and collaboration data explicitly.
- Test undo, paste, keyboard, mobile and assistive-technology workflows before cutover.