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.

componentWillReceiveProps warning with React 16.9

See original GitHub issue

Hello,

After updating react and react-dom to v16.9.0, this warning appears:

react-dom.development.js:11494 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.

Please update the following components: Motion

According to https://reactjs.org/blog/2019/08/08/react-v16.9.0.html#renaming-unsafe-lifecycle-methods, the componentWillReceiveProps is now deprecated and will be removed from the API on the next major version.

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:61
  • Comments:16

github_iconTop GitHub Comments

16reactions
jfrofficecommented, Feb 21, 2020

Any update on this ?

10reactions
JohnRoseDevcommented, Nov 22, 2021

How can an amazing project with 20k stars, conf presence (react europe talk), and a fantastic api be abandoned like this by the owner(s)? Completely understand if they don’t have time anymore for the project, no blame in that, but couldn’t one try in that case to delegate some ownership so someone can simply publish a new version of this package since the necessary code change is already there?

Read more comments on GitHub >

github_iconTop Results From Across the Web

componentWillReceiveProps warning in React 16.9.0 #30
Since React 16.9.0 this package will produce following warning into the console Warning: componentWillReceiveProps has been renamed, ...
Read more >
get warning "componentWillReceiveProps ... - Stack Overflow
This is a warning from react native. componentWillReceiveProps is a synchronous hook. Calling asynchronous function like data fetching ...
Read more >
Warning: componentWillMount has been Renamed, and is not ...
Learn what causes "Warning: componentWillMount has been renamed, and is not recommended for use ... Before class AppComponent extends React.
Read more >
Reactjs – componentWillReceiveProps has been renamed
react-dom.development.js:12466 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See for details.
Read more >
componentwillreceiveprops has been renamed stackoverflow
After updating react and react-dom to v 16.9.0, this warning appears: react-dom.development.js:11494 Warning: componentWillReceiveProps has been renamed, and is ...
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