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.

[BUG] - Warning: componentWillReceiveProps has been renamed

See original GitHub issue

Getting this warning !!!

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: NumericInput

Issue Analytics

State:
Created 3 years ago
Comments:5

Top GitHub Comments

3reactions

nccharlescommented, Apr 27, 2020

Badly this has no solution but changing this function and replace it with componentDidMount in the source code of the package. So you will have to wait till they update it or you could clone this repo and edit it by yourself then publish it to the npm and use your own library. Edit: I looked at the Pull requests and i found this one resolves this issue PR #49, so you will have to wait till they merge it, hope they do it soon.

I did it @YahiaBadr and it works properly in my app. Actually the source updated but they didn’t update NPM. I would recommend someone to do this.

2reactions

YahiaBadrcommented, Apr 25, 2020

Badly this has no solution but changing this function and replace it with componentDidMount in the source code of the package. So you will have to wait till they update it or you could clone this repo and edit it by yourself then publish it to the npm and use your own library. Edit: I looked at the Pull requests and i found this one resolves this issue PR #49, so you will have to wait till they merge it, hope they do it soon.