Replace dependency framer-motion with motion ^13.0.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
framer-motion → motion	dependencies	replacement	^13.0.0 → ^13.0.0

This is a special PR that replaces framer-motion with the community suggested minimal stable replacement version.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	poi-web-kai	4e969a3	Commit Preview URL Branch Preview URL	Sep 12 2026, 03:02 PM

[petit-chiba]

The diff swaps the framer-motion dependency for the renamed motion package and updates pnpm-lock.yaml accordingly, but the sole consumer (src/components/transition.tsx) still imports from 'framer-motion', which is no longer a direct dependency and won't resolve under pnpm's strict layout, breaking typecheck and build.

[petit-chiba]

Replacing the direct dependency framer-motion with motion breaks module resolution: src/components/transition.tsx:3 still imports { motion, HTMLMotionProps } from 'framer-motion', but framer-motion is now only a transitive dependency of the motion package. With pnpm's default strict node_modules layout (no .npmrc hoisting here), 'framer-motion' will not be resolvable from application source, so pnpm typecheck (tsc --noEmit) and vite build will fail with "Cannot find module 'framer-motion'". Fix: update the import in transition.tsx to 'motion/react' (the new package's React entrypoint), or keep framer-motion as a direct dependency.

[petit-chiba]

The diff replaces the framer-motion dependency with the renamed motion package and updates pnpm-lock.yaml accordingly, but the sole consumer (src/components/transition.tsx:3) still imports from 'framer-motion', which is no longer a direct dependency and won't resolve under pnpm's strict layout, breaking typecheck and build. GitHub's current base (a029d63) and head (95c76e6) match the caller-supplied revisions; PR #598 contains 1 commit, 1 issue comment (Cloudflare deploy status), 1 COMMENTED review and 1 review thread (petit-chiba[bot], package.json position 1) with no replies.

[petit-chiba]

This diff swaps the direct dependency framer-motion for motion (^13.0.0) and updates pnpm-lock.yaml so that framer-motion@13.1.1 is now only a transitive dependency of motion, but the sole consumer src/components/transition.tsx:3 still does import { type HTMLMotionProps, motion } from 'framer-motion'. This repo has no .npmrc/hoisting config, so under pnpm's default strict node_modules layout the import is no longer resolvable from app source, and CI (playwright.yml runs pnpm run build and pnpm run typecheck) will fail with "Cannot find module 'framer-motion'"; the component is imported by src/routes/index.tsx, explore.tsx and download.tsx, so it is reachable. Fix: update the import in src/components/transition.tsx to from 'motion/react' (both motion and HTMLMotionProps), or keep framer-motion as a direct dependency.