Nicheloom

Market intelligence for builders — see what's gaining traction before it's crowded.

JavaScript-first, open-source WYSIWYG DOCX editor

Details

External ID
46947229
Source
HN
Company
—
Product
JavaScript-first, open-source WYSIWYG DOCX editor
Website domain
github.com
Launched
Feb. 9, 2026
Cohort
—
Upvotes
130
Upvotes percentile
0.9137466307277629
Tags
—
Fetched at
Sept. 7, 2026, 9:26 p.m.
Updated at
Sept. 7, 2026, 9:26 p.m.

Description

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.

Enrichment

Theme
Claude integrations and coding agents
Vertical
Horizontal
Function
Dev tools
Audience
Developer
AI stance
Not AI
Project type
Hobby / open-source project
Normalized one-liner
javascript wysiwyg docx editor
Manually corrected
False

Could you build this?

Partial While an AI can iterate on code, implementing a robust, spec-compliant WYSIWYG editor for the massive and notoriously complex ISO/IEC 29500 (OOXML DOCX) specification requires deep parser engineering and rigorous layout engine work. Vibe coding can produce initial drafts, but handling arbitrary styling, tables, floating elements, and round-tripping DOCX XML without corruption requires extensive manual domain engineering.

What it would actually take: A complete DOCX WYSIWYG editor requires a custom tree/layout rendering engine in TypeScript, coupled with a robust OOXML parser (handling Open Packaging Conventions, drawingML, wordprocessingML namespaces). It necessitates automated visual regression pipelines comparing rendered canvases against native Word outputs across hundreds of real-world sample documents. The core challenge is matching Word's undocumented pagination, layout quirks, and legacy XML schemas.

Discussion

20 comments analyzed.

Competitors mentioned: LibreOffice, Commercial PDF/DOCX libraries, Browser-native document handling

Concerns raised: Complexity of DOCX spec (5000+ pages) makes full compatibility unrealistic, Undocumented Word behaviors deviate from spec, hard to handle, Last 10% of compatibility requires 90% of work, AI-generated imagery with copyright concerns, Replicating existing functionality as SaaS with added costs

Feature requests: Open source web DOCX editing capability, Live debugging and feedback loop visibility, Unit test harness for document generation validation

Competitors

Other products that read as similar to this one — 111 launches clear the similarity bar, closest 8 shown.

Attention rank: #18 of 112 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).

Launched 83 days after the earliest competitor.

Other launches for this product

Same idea, different domain

Nobody's really built a dev tools tool for Sales yet.