docx-editor

I've built tools using the agent in https://github.com/eigenpal/docx-editor. I can use my existing AI and don't need to connect to an external service, plus it is open source. Why would I use your solution instead?

Hey HN, I’m the author of the https://github.com/eigenpal/docx-editor, it’s an SDK that implements Word-compatible layout engine in Typescript. Today, we are releasing Word to markdown converter library. It’s open source and published under Apache 2.0 license. It uses our layout engine, so it can return accurate, per-page markdown blocks (with headers, footers, and image references). We also handle fonts (Google fonts as fallback) or let you pass your font files upfront for accurate content measurement. To our surprise, Word to per-page Markdown conversion is not a solved problem even in 2026! We initially faced this friction when preprocessing Word documents for agentic workflows. For our use case, it was important to represent per-page content in markdown. Initially, we ended up using LibreOffice sidecar to convert to PDF and then using

https://github.com/eigenpal/docx-editor (which I made) is great - since it's OS, the community helps a lot

The relevant non functional links should be listed in the comments. The OP was complaining they were not able to include links directly. I'm not sure about [1] [2] [3] in the main post but the show hn [A] or [B] thread should afaik have not been an issue. [A] https://news.ycombinator.com/item?id=46947229 [B] https://news.ycombinator.com/item?id=48228411 [1] https://docx-editor.dev/ [2] https://github.com/eigenpal/docx-js-editor [3] https://github.com/eigenpal/docx-editor Edit for additional show hn thread

For those interested here * is a similar project that I believe is *not* vibe coded posted a few weeks ago **. * https://github.com/eigenpal/docx-editor ** https://news.ycombinator.com/item?id=48228411

Thanks for reporting! We do have perf tests for editing docs over 50 pages, but something in the demo doc must indeed be slowing edits down, this is not expected behaviour. Filed an issue https://github.com/eigenpal/docx-editor/issues/590

We are working on an open-source .docx editor library for apps that need to edit Word documents in the browser. We just shipped 1.0. A lot of existing approaches convert .docx into HTML and lose document semantics along the way. Our editor parses OOXML directly and uses its own rendering+layout engine to produce paged documents with html/css. Edits round-trip back to .docx, so you’re always editing the document, not its representation. The core rendering engine is framework agnostic, with React and Vue ui adapters on top. It’s Apache 2.0. Happy to answer questions.

We needed a JS-first WYSIWYG DOCX editor and couldn't find a solid OSS option, most were either commercial or abandoned. As an experiment, we gave Claude Code the OOXML spec, a concrete editor architecture, and a Playwright-based test suite. The agent iterated in a (Ralph) loop over a few nights and produced a working editor from scratch. Core text editing works today. Tables and images are functional but still incomplete. MIT licensed.