ProseMirror
No written verdict yet. Here is what commenters said.
5recommend
3warn against
Nov 17, 2025first mention
Sep 2, 2026latest mention
Why people recommend it
“prosemirror-collab does give me offline editing. I use it literally every day, entirely without issue.”
“Lexical, Slate, and ProseMirror (especially ProseMirror, in our opinion!) are all excellent rich text libraries”
Show 2 more
“They also also are MUCH better at representing the user intent”
“it, too, is generally not a lot of code”
Author of the linked poston “Lies I was told about collaborative editing, Part 2:…”
Caveats and dissent
“One thing i've struggled with with Prosemirror (via TipTap)”
“so I guess Ill close the door on that idea”
Show 1 more
“which ironically talks about how hard prosemirror-collab is to debug”
Often compared with
Who recommends it in their own words
Threads where it came up
- Wordgard: The new in-browser rich-text editor from the creator of ProseMirror 6 mentions
- Lies I was told about collaborative editing, Part 2: Why we don't use Yjs 6 mentions
- Fine, I'll build my own text editor 1 mention
- Claude Fable 5: mid-tier results on coding tasks 1 mention
- Show HN: Atomic Editor – Obsidian-style live preview for CodeMirror 6 1 mention
- We're building a better rich text editing toolkit 1 mention
Data: prosemirror.json. Quotes are verbatim; the verdict and theme labels are written by a model from these comments, and every clause links to its sources.
All comments 19
“Haverbeke went on to create CodeMirror and ProseMirror.”
You are wrong, Lexical it is not in maintenance mode and continues to receive commits from contributors. 24k stars and counting. https://github.com/facebook/lexical
Seems like the contribution graph is on the highest for long time: https://github.com/facebook/lexical/graphs/contributors?from=6%2F29%2F2024 But Claude is playing part of it.
“One thing i've struggled with with Prosemirror (via TipTap)”
“doesn't seem like Prosemirror is going unmaintained. It will continue to be maintained”
For people who have dealt with react, this part might give some insight into that topic (https://wordgard.net/docs/prosemirror/#h-transactions-and-changes)? Nevertheless, it would be good if this could be addressed in the docs. I am not sure if this makes things easier for react interop, but this piece might be of interest too: > One of the biggest mistake blunders in ProseMirror is that the editor view does not get
“it seems that switching means doing quite some work”
“how I sync between the "livemodel" (in-memory replica of database state) and ProseMirror's model”
“so I guess Ill close the door on that idea”
“prosemirror-collab does give me offline editing. I use it literally every day, entirely without issue.”
“Lexical, Slate, and ProseMirror (especially ProseMirror, in our opinion!) are all excellent rich text libraries”
“We will have better support for ProseMirror's position mapping”
“which ironically talks about how hard prosemirror-collab is to debug”
“rewriting the y-prosemirror binding today”
Your part 1 post was one of the inspirations for that :) Specifically, it inspired the question: how can one let programmers customize the way edits are processed, to avoid e.g. the "colour" -> "u" anomaly*, without violating CRDT/OTs' strict algebraic requirements? To which the answer is: find a way to get rid of those requirements. *This is not just common behavior, but also features in a formal specification [1] o
“They also also are MUCH better at representing the user intent”
“it, too, is generally not a lot of code”
“which it converts to a separate ProseMirror tree on each update”
“construct a ProseMirror transaction that would turn the old tree into the new one”