chore(deps): motion and framer-motion 13 (major) - #76
Merged
Merged
Conversation
- framer-motion 12.38.0 -> 13.3.0 - motion 12.38.0 -> 13.3.0 (depends on framer-motion ^13, bumped together) Breaking change in 13.0.0: the optional @emotion/is-prop-valid auto-detection was removed in favour of an explicit <MotionConfig isValidProp>. This repo never installed @emotion/is-prop-valid, so nothing changes. All imports used here (motion, AnimatePresence, useAnimation, useMotionValue, useSpring, useInView, useAnimate, stagger, MotionConfig, cubicBezier, animate and the types) still exist in 13.3.0. Claude-Session: https://claude.ai/code/session_01KLWmWU1KLE2diUH14ryqv1
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One sentence
Major bump of
motionandframer-motionfrom 12 to 13 (left open for review because it is a major).Bumps
Breaking changes (13.0.0)
@emotion/is-prop-validauto-detection; consumers who relied on it must pass<MotionConfig isValidProp={isPropValid}>. This repo never installed@emotion/is-prop-valid, so no code change was needed. Source: https://github.com/motiondivision/motion/blob/main/CHANGELOG.mdMotionValueStateand dropped theuseDefaultValueTypeargument ofset(); not used here.src/(motion,AnimatePresence,useAnimation,useMotionValue,useSpring,useInView,useAnimate,stagger,MotionConfig,cubicBezier,animate,Variants,Transition,HTMLMotionProps,AnimationProps) is still exported in 13.3.0.motion@13depends onframer-motion@^13, so both move together.Supersedes dependabot #53 and #55 (which targeted 13.1.1).
Verification
pnpm typecheckcleanpnpm test: 4 files, 16 tests greenpnpm exec vitest run --config vitest.config.node.ts: 3 files, 21 tests greenpnpm buildpassesnext startsmoke:/200,/changelog200,/changelog/nope-xyz404,/faq200,/nope-404404Installed with
--ignore-scripts(isolated-vm postinstall fails under Node 26 locally; matches how Vercel builds).https://claude.ai/code/session_01KLWmWU1KLE2diUH14ryqv1