Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: remove unused framer features #8347

Closed
wants to merge 2 commits into from

Conversation

mezotv
Copy link

@mezotv mezotv commented Mar 10, 2024

📝 Description

Changes the motion import to the more lightweigth m component.

⛳️ Current behavior (updates)

Currently uses the motion import which loads all of the features even the ones you don't need.

🚀 New behavior

Uses the lightweight m component with only the animation features loaded into. Since thats the only thing the components use.

💣 Is this a breaking change (Yes/No):

Not a breaking change!

📝 Additional Information

Docs for this change: https://www.framer.com/motion/guide-reduce-bundle-size/

Copy link

changeset-bot bot commented Mar 10, 2024

🦋 Changeset detected

Latest commit: 4f54b3d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 3 packages
Name Type
@chakra-ui/react Patch
@chakra-ui/test-utils Patch
@chakra-ui/docs Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Mar 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
chakra-ui-storybook ❌ Failed (Inspect) Mar 12, 2024 0:48am
chakra-ui-website ❌ Failed (Inspect) Mar 12, 2024 0:48am

@segunadebayo
Copy link
Member

Thanks for working on this.

Closing this in favor of the upcoming v3 version which no longer requires framer-motion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants