chore(deps): upgrade motion to 13.x#106

merged1
chore/deps-vitest-4
chore/deps-motion-13
openedAug 26, 2026byMMihai
View on GitHubTwo-way sync enabledPR last imported 16d ago

motion 12.43.0 -> 13.1.1. no code changes needed.

sourced from motion.dev/docs/react-upgrade-guide and the upstream CHANGELOG, 13.x entries only:

  • 13.0.0 — the only breaking change in the whole major: dropped the optional @emotion/is-prop-valid dep in favour of explicit <MotionConfig isValidProp={isPropValid}>. only bites emotion / styled-components users. we have neither, and no motion.create(StyledX) anywhere
  • 13.0.0 also fixes hardware-accelerated SVG final style on animation complete, and AnimatePresence marking nodes safe to remove
  • 13.1.0 — Reorder multidimensional, auto axis detection, RTL
  • 13.1.1 — guards window access in non-browser runtimes, better AnimatePresence compat with React 19 strict mode

last two are straight wins for us on React 19 + Next SSR.

usage inventory, all still valid under v13:

  • components/ui/animated-group.tsx, animated-background.tsx, progressive-carousel.tsx
  • components/features/landing/faq.tsx, feature-section-with-hover-effects.tsx
  • components/admin/blog/create-blog-dialog.tsx, edit-blog-dialog.tsx
  • lib/animations.ts

checks: typecheck clean, 203/203 tests, build ok.

browser verification (static checks can't see animation regressions), dev server + isolated Chrome:

  • desktop 1280x720 — /ro home scrolled in 6 steps, AnimatedGroup reveals, feature-section useInView reveal, carousel slat transition + pagination all correct. /ro/faq accordion open animations correct
  • mobile iPhone 14, confirmed 392x849 — /en home scrolled in 10 steps, same reveals correct. /en/faq expanded AND collapsed, which confirms the AnimatePresence exit path still runs (the thing most likely to break silently on this major)
  • zero motion-related console errors; only pre-existing Clerk/Cookiebot/analytics noise

two gaps worth a look:

  • components/ui/animated-background.tsx uses layoutId shared-layout but is imported by nothing, so it got no runtime coverage
  • the two admin blog dialogs (AnimatePresence mode="wait") are behind Clerk auth and weren't visually checked. mode="wait" had no v13 changes, but that's the honest gap

RNGO-44 · part of RNGO-40 (dependency upgrade sweep) https://linear.app/mihaicrisan/issue/rngo-44/upgrade-motion-to-1311-pr-106

Checks

5 successful
All checks passed
4ffbe7a
Synced from GitHub

Greptile Summary

The PR upgrades Motion and its resolved supporting packages from 12.43.0 to 13.1.1 without changing application code.

  • Updates the direct motion dependency range in package.json.
  • Refreshes bun.lock resolutions for Motion, Framer Motion, Motion DOM, and Motion Utils.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

FilenameOverview
package.jsonUpdates Motion to the 13.1.1 release line; existing imports and API usage show no established compatibility failure.
bun.lockConsistently resolves Motion and its related packages to compatible 13.x versions.

Reviews (2): Last reviewed commit: "chore(deps): upgrade motion to 13.x" | Re-trigger Greptile

Added 1 commit

  • chore(deps): upgrade motion to 13.x4ffbe7a