Move data fetching code or side effects to componentDidUpdate. #119
Comments
|
I have the same issue!!!! |
|
I'm also facing this issue in react-native 0.61.5 tried this command also but same issue ( npx react-codemod rename-unsafe-lifecycles) |
|
react-dom.development.js:88 Warning: componentWillUpdate has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.
Please update the following components: Lottie It's in react.js
|
zwliew
added a commit
to opengovsg/postmangovsg
that referenced
this issue
Mar 24, 2021
The original react-lottie library seems to be abandoned and still uses deprecated React lifecycle methods [1]. These methods will be removed in React 17. Hence, migrate to lottie-react instead, which fixes the issue and is expected to have React 17 support [2]. [1]: chenqingspring/react-lottie#119 [2]: Gamote/lottie-react#29
This was referenced Mar 24, 2021
lamkeewei
pushed a commit
to opengovsg/postmangovsg
that referenced
this issue
Mar 30, 2021
The original react-lottie library seems to be abandoned and still uses deprecated React lifecycle methods [1]. These methods will be removed in React 17. Hence, migrate to lottie-react instead, which fixes the issue and is expected to have React 17 support [2]. [1]: chenqingspring/react-lottie#119 [2]: Gamote/lottie-react#29
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Rename componentWillUpdate to UNSAFE_componentWillUpdate 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-lifecyclesin your project source folder.Issue poping all the time that may need fixing
The text was updated successfully, but these errors were encountered: