onUpdate() is called 60x per second (once per frame). That's how framer motion works. That is the right behaviour. If you wanted to move a div to the right, for example, you could just move it by 1px in every onUpdate() call and it would start moving. That's roughly how animations work on the web.

Can't reproduce the error. Are you talking about the covercraft.io or the codesandbox? Also, what browser are you using?

Glad I could help. Thanks for spreading the word :)

Glad you liked it! ❤️

Very cool! I never knew that selection has so much cool stuff to fiddle around with. A quick question: wouldn't you want to return an unsubscribe() function from the event listener in your useEffect() to clean up the listener when the component unmounts? Thanks for the article :D

Thanks for the article! I tend to like prop destructuring. In small components there's usually not enough going on for me to get confused about which variables come from where, even without using props.x . When a component starts taking too many props, it's usually a sign for me to break it into smaller components or think about what props are actually needed. If a component does take a lot of props, I like destructuring and defining a type interface for props so it's clear what props that component takes. I agree that writing props. every time is not too much of an overhead, but I think destructuring looks cleaner. Thanks for your take, very interesting :)

Thank you for reading :)

Glad I can get you excited for animation!

I'm afraid I'm not familiar with duolingo exercises. DM me, if you need any help.

Thank you :)