February 10, 2026
Ctrl+B for Beef
Show HN: JavaScript-first, open-source WYSIWYG DOCX editor
Open‑source Word‑in‑browser drops; vets say “good luck”, newbies ask “is it Google Docs?”
TLDR: An open-source browser editor for Word files just launched, aiming for true “what you see is what you get” editing. The community split: veterans warn Word’s weird file quirks will crush it, newbies ask if it’s just Google Docs, and fans hail a rare open alternative worth rooting for.
A new open‑source “what you see is what you get” editor claims you can open, edit, and save Microsoft Word files right in the browser—no server, no download, just click and type. It’s built for React (a popular web toolkit) and promises Word‑level fidelity, plugins, and a slick toolbar. Think Google Docs vibes, but DIY and open for everyone to remix. The devs even brag about zero server dependencies and a plugin system to extend features.
Cue the comment section exploding. A veteran swoops in with a reality check: “Word is the spec, not OOXML,” referring to the Office file format. Translation: the official rules don’t match how Word actually behaves, and that’s a bug factory. He says it took two minutes to find issues and warns of “hundreds” of hidden edge cases, turning the launch thread into a cautionary tale. Meanwhile, newcomers pop in with “So it’s like Google Docs?” and the accidental meme of the day: “Whats a Ralph loop?”, a delightful non sequitur that commenters adopted as shorthand for “I’m lost.”
Balancing the doom and gloom, fans cheer the dream of a truly open, browser‑based Word alternative. If this editor’s page breaks match Word, one commenter says, “this is huge.” The vibe: hopeful, skeptical, and extremely popcorn‑worthy.
Key Points
- •@eigenpal/docx-js-editor is an open-source WYSIWYG DOCX editor for React that runs entirely in the browser with no server required.
- •Installation is via npm, with a Quick Start showing how to load a .docx, edit it, and save via an ArrayBuffer.
- •Next.js/SSR integration requires dynamic import or lazy loading to avoid DOM-related server-side rendering issues.
- •The API includes props for document sources, read-only mode, UI controls, callbacks, and ref methods like save(), getDocument(), setZoom(), and print().
- •A plugin system supports extensions (e.g., Docxtemplater), and features include Word-like fidelity, rich formatting, tables, images, undo/redo, find & replace, and print preview under an MIT license.