npm upgrade
Homeframer-motion 11 → 12
11.18.2 → 12.43.0. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.
framer-motion 12.43.0 removes or renames exports your code may import.
- Removed
- 46
- Renamed
- 0
- Signature changes
- 1
- Types removed
- 0
- Newly deprecated
- 0
- Added
- 10
Does this break your code?
Run this in your project. It compares both releases against the names your code actually imports, locally, with no account and nothing sent to lurq:
npx lurqrun check-upgrade --upgrade framer-motion@11.18.2..12.43.0
To have your coding agent check upgrades like this before it writes them, connect lurq to Claude Code, Cursor, VS Code or Codex:
npx lurqrun
Removed
Gone at runtime, with no replacement found under another name. Imports of these fail.
- AcceleratedAnimationclass
- FlatTreeclass
- MotionValueclass
- animateValuefunction
- anticipatefunction
- backInobject
- backInOutobject
- backOutobject
- cancelFrameobject
- cancelSyncobject
- circInfunction
- circInOutobject
- circOutobject
- clampfunction
- colorobject
- complexobject
- createRendererMotionComponentfunction
- cubicBezierfunction
- easeInobject
- easeInOutobject
- easeOutobject
- findSpringfunction
- frameobject
- frameDataobject
- frameStepsobject
- inertiafunction
- interpolatefunction
- invariantobject
- isDragActiveobject
- isMotionValuefunction
- keyframesfunction
- mirrorEasingfunction
- mixfunction
- motionValuefunction
- noopobject
- pipefunction
- progressobject
- pxobject
- reverseEasingfunction
- springfunction
- staggerfunction
- stepsfunction
- syncobject
- timeobject
- transformfunction
- wrapfunction
Signature changes
Still exported, but the number of arguments it reads changed.
- createScopedAnimate1 → 0 arguments
An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Aug 8, 2026. framer-motion on lurq.