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.

in react @16.9.0 Warning:componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

See original GitHub issue

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks 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.

Issue Analytics

State:
Created 4 years ago
Reactions:18
Comments:8 (4 by maintainers)

Top GitHub Comments

10reactions

jalvarsoncommented, Oct 17, 2019

Wondering the same. Is this library still maintained @loktar00 ?

4reactions

loktar00commented, Jul 8, 2020

@smolak I might as well, was on vacation just got back yesterday… kind of want to look at the entire component with fresh eyes honestly. It might become a 3.0 with the changes required.