framer-motion
14.7.1 · 27 Oct 2026MIT45.3M / weekRepositoryHomepagenpmAtom feed
Upgrading framer-motion from 11.3.30 to 11.18.2
55 releases in betweennotes for 54
- 1+
- change to make
- 0
- advisories fixed
- 19+
- new
- 44+
- fixes
Counted from 54 of 55 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- breaking11.17.0
Release by release
- fixed
Animations with
transformTemplatenot hardware accelerated.
- fixed
- fixed
AnimatePresencetypes in React 19. - fixed
SVG with
transformnot always setting styles correctly on mount.
- fixed
- new
Adding
animateSequenceto perform animation sequences via WAAPI for a tiny bundlesize. - fixed
Missing
AnimationControlstype export.
- new
- fixed
Remeasure SVG when size/position changes to ensure correct
transform-origin.
- fixed
- new
Added
propagatetoAnimatePresence. This prop allows parent exit animations to be propagated to children.
- new
- fixed
Fixing timelines where a string label is used as the first segment.
- fixed
11.16.6nothing new or fixed in the note
- fixed
Fix type of
attachTimelinewhenskipLibCheckis disabled.
- fixed
6 other lines we could not sort, mostly version bumps
- 11.16.6
More movement values like
heightandtopare now blocked by reduced motion. - 11.11.12
Adding
"motion"package. - 11.11.12
Replaced Motion One (see upgrade guide).
- 11.11.9
will-changeis now no longer automatically managed withoutuseWillChange. - 11.6.0
Values added to
will-changenow stay there for their lifespan to prevent GPU thrashing and weird Safari subpixel jitters. - 11.5.0
motion()andm().