Guide eigenpal → OpenOOXML
Migrating from eigenpal to OpenOOXML
eigenpal was deprecated when its maintainers moved to a commercial product. OpenOOXML is an independent Apache 2.0 implementation of the same public API — an API-compatible, open-source alternative, so migration is a package swap, not a rewrite.
01 Zero-change option
Keep your imports, swap the package
npm aliases let you install @betteroffice/docx under the old eigenpal name. Existing imports keep working — no code changes.
$
npm i @eigenpal/docx-editor-core@npm:@betteroffice/docx02 Full migration
Move to the @betteroffice scope
For new code and long-term maintenance, replace the deprecated eigenpal packages with their BetterOffice equivalents — the npm packages built on the OpenOOXML engines.
$
npm uninstall @eigenpal/docx-editor-core$
npm install @betteroffice/docx| Deprecated eigenpal package | BetterOffice replacement | |
|---|---|---|
| @eigenpal/docx-editor-core | @betteroffice/docx | |
| @eigenpal/docx-editor-react | @betteroffice/docx-react | |
| @eigenpal/docx-editor-vue | @betteroffice/docx-vue |
imports, before / after
- import { DocxEditor } from "@eigenpal/docx-editor-core";
+ import { DocxEditor } from "@betteroffice/docx";03 FAQ
Frequently asked questions
- Is the API identical to eigenpal?
- Yes. OpenOOXML v1 implements the same public API — same classes, same methods, same events — in an independent codebase, so it works as a drop-in replacement.
- Is OpenOOXML actively maintained?
- Yes. The packages receive regular fixes and releases, and the engines are written in Rust with WebAssembly builds for the web.
- What license does it use?
- Apache 2.0 — permissive and free for commercial use.
- Who is behind OpenOOXML?
- It was started by a contributor to the original eigenpal editor, together with a community of former eigenpal users. Development happens in the open on GitHub.