You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
React 19 will be officially released in June/July 2024 and it removes the deprecated ReactDOM.findDOMNode utility. It appears that this will prevent react-quill users from upgrading to React 19.
I recently installed React 18.3 (which was released about a week ago) and it started issuing warnings about this:
Warning: findDOMNode is deprecated and will be removed in the next major release. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node
I didn't see another issue opened regarding the removal of findDOMNode so I thought I'd bring this issue to the attention of the maintainers (@zenoamaro@alexkrolick).
Thank you for your on-going maintenance of this project!
Ticket due diligence
I have verified that the issue persists under ReactQuill v2.0.0-beta.2
I can't use the beta version for other reasons
ReactQuill version
master
v2.0.0-beta.2
v2.0.0-beta.1
1.3.5
1.3.4 or older
Other (fork)
The text was updated successfully, but these errors were encountered:
Here's a PR that proposes a fix for this issue: #980. Not sure if the maintainer(s) are actively monitoring, but I have been testing it locally and it works great.
React 19 will be officially released in June/July 2024 and it removes the deprecated
ReactDOM.findDOMNode
utility. It appears that this will preventreact-quill
users from upgrading to React 19.I recently installed React 18.3 (which was released about a week ago) and it started issuing warnings about this:
I didn't see another issue opened regarding the removal of
findDOMNode
so I thought I'd bring this issue to the attention of the maintainers (@zenoamaro @alexkrolick).Thank you for your on-going maintenance of this project!
Ticket due diligence
v2.0.0-beta.2
ReactQuill version
The text was updated successfully, but these errors were encountered: