Offering to help with maintenance, starting with triage

Hi @zenoamaro, @alexkrolick — I'd like to offer some help here, if it's welcome.

I've been using react-quill and recently sent #1050. Before opening this I looked at where the repo currently stands:

• Last release is 2.0.0, published August 2022
• Last commit is February 2025
• 405 open issues and 27 open pull requests
• peerDependencies is still ^16 || ^17 || ^18

The React 19 gap is the one people keep hitting. #972 ("React 19 will remove findDOMNode") has been open since May 2024, and #989 has 30 comments from people trying to get the library working with Next 15. Since React 19 removed findDOMNode, the component throws at mount, and there is no version of react-quill that installs cleanly against React 19.

For context on the scale: react-quill is at roughly 27.9M downloads a month, so this is a lot of people working around the same thing.

#1050 is my attempt at the fix — it replaces the findDOMNode call with a ref, widens the peer range to include React 19, and adds tests for the case where children renders something that isn't a host element. The existing suite passes.

What I'm actually asking for: not write access.

If you're open to it, I'd like triage permission to start — labelling, closing duplicates, pointing the many React 19 reports at a single thread, and answering the questions that have clear answers. That's the part that doesn't need trust in my judgment about the code, and it's where the backlog is worst. A good share of the 405 is likely already resolved or duplicated.

If that turns out to be useful over a few weeks, we can talk about whether it makes sense to go further. If you'd rather keep everything as is, that's completely fine — I'll keep sending PRs the normal way.

Either way, thanks for building this. It's been in a lot of my projects.