What code you own after installing editorcn and how it affects customization.
Editorcn is designed so that you own the code after installation. How much you own depends on the install method.
Registry install (recommended)
When you install via the shadcn registry with npx shadcn@latest add @editorcn/editor, the CLI copies every source file directly into your project. The editor becomes part of your codebase — you can modify anything without fighting a dependency.
Full customization: Every control, extension, UI component, and style is yours to edit. Want to change the toolbar layout? Edit rte-text-editor.tsx. Want different resize behavior? Edit resizable-node-view.tsx.
No dependency lock-in: Your editor doesn't break when editorcn publishes a new version. You control when and if you update.
Direct imports: Import from your project's components directory, not from a node_modules package:
import { RichTextEditor, Link } from "@/components/editor";import "@/components/editor/style.css";
Peerdependencies are not copied — @tiptap/* packages remain in node_modules. You own the UI layer and extensions that are specific to editorcn.
npm install
When you install @editorcn/editor from npm, you get the compiled JavaScript and type definitions in node_modules. The source files remain in the published package and are not copied into your project.