Skip to content

fix(deps): replace dependency framer-motion with motion ^12.0.0#164

Merged
SamuelIVX merged 1 commit into
mainfrom
renovate/framer-motion-replacement
Jul 14, 2026
Merged

fix(deps): replace dependency framer-motion with motion ^12.0.0#164
SamuelIVX merged 1 commit into
mainfrom
renovate/framer-motion-replacement

Conversation

@SamuelIVX

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
framer-motionmotion dependencies replacement ^12.0.0^12.0.0

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


Configuration

📅 Schedule: (in timezone America/New_York)

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate.

@coderabbitai

coderabbitai Bot commented Jul 13, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated the animation package used by the application to the latest motion library.

Walkthrough

The project replaces its framer-motion dependency with motion, keeping the version range at ^12.0.0.

Changes

Motion dependency update

Layer / File(s) Summary
Motion dependency declaration
package.json
Replaces framer-motion with motion at version ^12.0.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the dependency swap from framer-motion to motion ^12.0.0.
Description check ✅ Passed The description is clearly related to the dependency replacement and matches the PR objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/framer-motion-replacement

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 19: Update the imports in About, Contact, Experience, Hero, Works, and
SectionWrapper to use motion/react instead of framer-motion, preserving their
existing imported symbols. Regenerate the lockfile so the direct motion
dependency is reflected without the remaining transitive framer-motion coupling.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5e77d620-5e6d-45bd-b66c-f31052b0cc62

📥 Commits

Reviewing files that changed from the base of the PR and between 1b634fe and fe8ab88.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json
📜 Review details
⏰ Context from checks skipped due to timeout. (3)
  • GitHub Check: Lint Code Base
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: Analyze (actions)

Comment thread package.json
"@react-three/drei": "^9.121.2",
"@react-three/fiber": "^8.17.12",
"framer-motion": "^12.0.0",
"motion": "^12.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🔵 Trivial | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== package.json ==\n'
sed -n '1,120p' package.json

printf '\n== package-lock.json references ==\n'
rg -n '"framer-motion"|"motion/react"|"motion"' package-lock.json package.json src || true

printf '\n== import sites ==\n'
rg -n 'from\s+[\'"]framer-motion[\'"]|from\s+[\'"]motion/react[\'"]|import\s+.*motion.*from' src || true

Repository: SamuelIVX/SamuelIVX.github.io

Length of output: 2164


Switch the remaining imports to motion/react.
src/components/About.jsx, src/components/Contact.jsx, src/components/Experience.jsx, src/components/Hero.jsx, src/components/Works.jsx, and src/hoc/SectionWrapper.jsx still import from framer-motion even though motion is now the direct dependency. Updating these imports and regenerating the lockfile removes the transitive dependency coupling.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 19, Update the imports in About, Contact, Experience,
Hero, Works, and SectionWrapper to use motion/react instead of framer-motion,
preserving their existing imported symbols. Regenerate the lockfile so the
direct motion dependency is reflected without the remaining transitive
framer-motion coupling.

@SamuelIVX
SamuelIVX merged commit 1c87854 into main Jul 14, 2026
6 checks passed
@SamuelIVX
SamuelIVX deleted the renovate/framer-motion-replacement branch July 14, 2026 00:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant