componentWillUpdate has been renamed,

[payandeh]

Warning: componentWillUpdate 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.
• 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-lifecycles in your project source folder.

Please update the following components: Lottie

[mrados7]

Yep, someone needs to fix this :/

[thomazcapra]

Is this repo being mantained by someone?

[graemeblackwood]

The owner of this repo, @chenqingspring, has barely done anything on any of their repos in the last year: https://github.com/chenqingspring

I've been looking through all the repo forks but it's hard to find one that is maintained.

[lazysergey]

@thomazcapra @fake230 @graemeblackwood we forked this, added typescript and rewrote some parts so now it fits current lottie-web typings/naming. see https://github.com/crello/react-lottie

[mifi]

I never got any of the existing lottie-web React wrappers to correctly react to changes in props and properly play segments. So I made a complete rewrite using modern hooks only: react-lottie-player. No more deprecation warnings!

[tavareshenrique]

@lazysergey Thanks for that, bro, it works for me!

[Girish3002]

@lazysergey Thanks , now works fine for me

[ngoctan3006]

@lazysergey It not working for me ☹️

Warning: Using UNSAFE_componentWillUpdate in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.
* Move data fetching code or side effects to componentDidUpdate.
Please update the following components: Lottie2

[ValentinShtankoAimtraction]

Yo, issue from 2019