Guide eigenpal → OpenOOXML
Migrating from eigenpal to OpenOOXML
eigenpal was deprecated when its maintainers moved to a commercial product. OpenOOXML is the Apache 2.0 community continuation of the last open release — 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 @openooxml/docx under the old eigenpal name. Existing imports keep working — no code changes.
$
npm i @eigenpal/docx-editor-core@npm:@openooxml/docx02 Full migration
Move to the @openooxml scope
For new code and long-term maintenance, replace the deprecated eigenpal packages with their OpenOOXML equivalents.
$
npm uninstall @eigenpal/docx-editor-core$
npm install @openooxml/docx| Deprecated eigenpal package | OpenOOXML replacement | |
|---|---|---|
| @eigenpal/docx-editor-core | → | @openooxml/docx |
| @eigenpal/docx-editor-react | → | @openooxml/docx-react |
| @eigenpal/docx-editor-vue | → | @openooxml/docx-vue |
imports, before / after
- import { DocxEditor } from "@eigenpal/docx-editor-core";
+ import { DocxEditor } from "@openooxml/docx";03 FAQ
Frequently asked questions
- Is the API identical to eigenpal?
- Yes. OpenOOXML v1 is a drop-in replacement for the last open eigenpal release — same classes, same methods, same events.
- Is OpenOOXML actively maintained?
- Yes. The v1 packages receive fixes and releases, and a Rust/WASM rewrite (v2) is on the roadmap.
- What license does it use?
- Apache 2.0 — the same license eigenpal used before it was deprecated.
- 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.