Open NoriSte opened 5 years ago
Since updating to React 16.9.0 I've also been getting this warning and the suggestions:
- Move data fetching code or side effects to componentDidUpdate.
- Rename componentWillUpdate to UNSAFEcomponentWillUpdate 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.
Same issue we need a fix for the react 16.9.0.
Could it be moved into componentDidUpdate
and compare prevProps
? Sorry for the lazy response, but this is also an issue for us as we update our codebase and I just got around to investigating this.
Edit: Ah, it says to do that in the suggestions... 🤕
Any update on this?
Guys did you drop further development? You didn't released since 14 Jun 2018
is there a replacement for this lib?
I made a complete rewrite using modern hooks: react-lottie-player. No more deprecation warnings!
use the latest version of lottie ===>>>> lottie-web react-lottie or web-react-lottie are not updated
Hi guys I've just enabled React.strictMode for my app and the only warning I get is related to Lottie
That's the indicted code, is there a safe way to remove the hook without compromising how Lottie work?
Thank you for all 😊 Stefano