framer-motion
14.7.1 · 27 Oct 2026MIT45.3M / weekRepositoryHomepagenpmAtom feed
Upgrading framer-motion from 7.5.3 to 7.10.3
33 releases in betweennotes for 32
- 3+
- changes to make
- 0
- advisories fixed
- 9+
- new
- 19+
- fixes
Counted from 32 of 33 release notes. Advisories are counted from the advisory database, in full.
Before you upgrade
Tick each one off as you go- breaking7.7.2
- breaking7.7.0
- breaking7.7.0
Release by release
7.10.3nothing new or fixed in the note
- fixed
Adding support for all easing functions with WAAPI.
- fixed
- fixed
Fixed type inference of
useMotionValueEvent.
- fixed
- new
.on()event method toMotionValue. - new
"animationStart","animationComplete","animationCancel"and"change"events forMotionValue. - new
useMotionValueEventhelper method for adding events.
- new
- fixed
Fixing mapping Motion easing names to WAAPI.
- fixed
- new
Hardware-accelerated
opacityanimations.
- new
7.8.1nothing new or fixed in the note
- new
Added private APIs for starting initial animations before React hydration and handing off to the component after hydration.
- new
8 other lines we could not sort, mostly version bumps
- 7.10.3
Firing
animateChangesinuseLayoutEffectrather thanuseEffectto ensure optimised appear animations are handed off before paint. - 7.8.1
Refactored animation pipeline to better accomodate WAAPI.
- 7.7.1
Removed
style-value-typesandframesyncas external dependencies. - 7.6.18
Removed
popmotionas external dependency. - 7.6.11
Further layout animation performance enhancements.
- 7.6.10
Removing read of (currently unused)
positionstyle as it's erroneously breaking a test in Framer. - 7.6.9
Only updating projection calculations for dirty nodes.
- 7.6.8
Reducing number of scroll reads during layout animations.