lurq

npm upgrade

Home

framer-motion 10 → 11

10.18.0 → 11.18.2. What the package's exports lost, renamed or changed between the two releases, from lurq's extraction of both published tarballs.

framer-motion 11.18.2 removes or renames exports your code may import.

Removed
4
Renamed
0
Signature changes
0
Types removed
0
Newly deprecated
0
Added
11

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@10.18.0..11.18.2

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

Quickstart

Removed

Gone at runtime, with no replacement found under another name. Imports of these fail.

  • checkTargetForNewValuesobject
  • createDomMotionComponentfunction
  • createMotionComponentfunction
  • warningobject

An export diff shows what a release removed or re-signatured, not behaviour changes: read the changelog for those. Extracted Aug 10, 2026. framer-motion on lurq.