Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
upgrade to React 17
See original GitHub issueIssue
This package currently throws a warning with React 17 as it still uses React 16. Seeing as previous commits fixed the deprecations 16 threw for what would change in 17, this should hopefully be a trivial change.
npm WARN react-quill@2.0.0-beta.2 requires a peer of react-dom@^16.0.0 but none is installed. You must install peer dependencies yourself.
ReactQuill version
v2.0.0-beta.2
Issue Analytics
- State:
- Created 2 years ago
- Reactions:31
- Comments:16
Top Results From Across the Web
React v17.0 – React Blog
React 17 enables gradual React upgrades. When you upgrade from React 15 to 16 (or, this time, from React 16 to 17), you...
Read more >Upgrading to React 17 - Medium
We finally upgraded our app to React v17 from v16. The v17 was released almost 3 years after the previous major release.
Read more >Upgrading to React 17 and Webpack 5 | by Chameera Dulanga
This article will discuss the steps to upgrading a React project to React 17 and Webpack 5 with my own set of tips...
Read more >React upgrade from 16 to 17 - Stack Overflow
I'm trying React upgrade from 16 to 17. What I should take care of? I have a lot of packages installed. how to...
Read more >Upgrading to React 17 - DEV Community
Migrating an unejected Create React App project · Install updated packages · Remove old installation and version lock file · Reinstall · Rebuild....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi Chaps, I’m suffering from this problem too, any chance of upgrading the dependency to React 17 please?
Also, there are warnings about
componentWillReceivePropsandcomponentWillUpdatebeing used that should be taken care of.However, looking at this comment and the number of issues alone, it looks like this library isn’t maintained anymore…