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.

Using expired functions :componentWillReceiveProps has been renamed

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.

Please update the following components: Tour

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:9 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
vhflatcommented, Nov 20, 2019

@elrumordelaluz when will this be released?

2reactions
thomassiewcommented, Dec 13, 2019

Looking forward to the release too. any date of release?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Warning: componentWillReceiveProps has been renamed ...
componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.
Read more >
get warning "componentWillReceiveProps has been renamed ...
Use componentDidMount whenever you need operate async operation ... Then you should search the code and find "componentWillReceiveProps".
Read more >
componentWillReceiveProps has been renamed - React Studio
In React 17. x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx...
Read more >
componentwillreceiveprops has been renamed stackoverflow
The reason is that the componentWillReceiveProps method is being deprecated by React and it is still used in the Grid. The team is...
Read more >
componentwillmount has been renamed, and is not ... - You.com
You're getting this warning because componentWillMount is deprecated in newer React versions. If you're not using componentWillMount anywhere then one of your ...
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