question-mark
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.

I'm getting a yellow warning message on the console

See original GitHub issue

I just installed a new version of quill and I’m using react v16. There’s a yellow warning message that appears:

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.`


* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.


Please update the following components: Quill

Use of Mutation Events is deprecated. Use MutationObserver instead.

How do I fix this?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:7

github_iconTop GitHub Comments

3reactions
VladLegkowskicommented, Jan 25, 2021

im using react and react dom 17 and getting this error with

    "react-quill": {
      "version": "2.0.0-beta.2",
      "resolved": "https://registry.npmjs.org/react-quill/-/react-quill-2.0.0-beta.2.tgz",
      "integrity": "sha512-jzoq57Mt216sCOr59OC6aMgmckdAh3BgKgEqYI/FcS26JwCMlXMgGu7Dc7TApzObax9dwOWbr6lT8cEWxigyVA==",
      "requires": {
        "@types/quill": "^1.3.10",
        "lodash": "^4.17.4",
        "quill": "^1.3.7"
      }
    },
npm WARN react-quill@2.0.0-beta.2 requires a peer of react@^16.0.0 but none is installed. You must install peer dependencies yourself.
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.

Can I ask you if it is on the roadmap to update the dependencies to react 17, thanks

2reactions
Saibamencommented, Nov 5, 2020

When 2.0 will be released?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Display yellow warning message in console - Stack Overflow
warning(message) returns Uncaught TypeError: console. warning is not a function.
Read more >
warning black box console - Apple Support Communities
I had this black box pop up on the bottom of my Mac pro with yellow letters "Warnin" "AY 7:36" When I opened...
Read more >
The Console Icon is issuing a black warning box sign with ...
The Console Icon is issuing a black warning box sign with yellow type. How do I eliminate the problem?
Read more >
warning symbol in plot - The Observable Forum
A little yellow warning symbol is showing up in a plot I'm generating with Plot . It looks like this: image.
Read more >
Dashboard Warning Lights Explained | Quick Tip - YouTube
Quick explanation of some of the less common dashboard warning lights. For more information contact:Don Wheaton Chevrolet Buick GMC ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found