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

chore(deps): framer-motion versions #3308

Merged
merged 4 commits into from
Jun 30, 2024
Merged

Conversation

wingkwong
Copy link
Member

@wingkwong wingkwong commented Jun 23, 2024

Closes #

📝 Description

  • bump frame-motion in peerDependencies (set to 11.0.22 because of previous only two keyframes currently supported with spring and inertia animations bug fix)
  • sync frame-motion in devDependencies across packages

⛳️ Current behavior (updates)

Please describe the current behavior that you are modifying

🚀 New behavior

Please describe the behavior or changes this PR adds

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

📝 Additional Information

Summary by CodeRabbit

  • Dependencies Update
    • Updated the framer-motion dependency to version ^11.1.7 across various components.
    • Adjusted peerDependencies for framer-motion to >=11.0.22 for better compatibility.

These updates ensure improved performance and compatibility with the latest features of framer-motion.

Copy link

linear bot commented Jun 23, 2024

Copy link

vercel bot commented Jun 23, 2024

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

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 23, 2024 3:06pm
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 23, 2024 3:06pm

Copy link

changeset-bot bot commented Jun 23, 2024

🦋 Changeset detected

Latest commit: b4167eb

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

This PR includes changesets to release 22 packages
Name Type
@nextui-org/accordion Patch
@nextui-org/autocomplete Patch
@nextui-org/button Patch
@nextui-org/calendar Patch
@nextui-org/card Patch
@nextui-org/dropdown Patch
@nextui-org/modal Patch
@nextui-org/navbar Patch
@nextui-org/popover Patch
@nextui-org/ripple Patch
@nextui-org/select Patch
@nextui-org/snippet Patch
@nextui-org/tabs Patch
@nextui-org/tooltip Patch
@nextui-org/system Patch
@nextui-org/framer-utils Patch
@nextui-org/react Patch
@nextui-org/date-picker Patch
@nextui-org/slider Patch
@nextui-org/listbox Patch
@nextui-org/menu Patch
@nextui-org/aria-utils 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
Contributor

coderabbitai bot commented Jun 23, 2024

Walkthrough

This update primarily focuses on synchronizing the version requirements for the framer-motion dependency across various components within the system. Several core components and utilities had their framer-motion versions updated to ensure compatibility and consistency. The changes include modifications to both peerDependencies and dependencies, reflecting an upgrade to more recent versions of the library.

Changes

File Path Change Summary
.../accordion/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../autocomplete/package.json Updated framer-motion peer dependency to >=11.0.22.
.../button/package.json Updated framer-motion peer dependency to >=11.0.22.
.../calendar/package.json Updated framer-motion dependency to ^11.1.7.
.../card/package.json Updated framer-motion dependency to ^11.0.22.
.../dropdown/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../modal/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../navbar/package.json Updated framer-motion peer dependency to >=11.0.22.
.../popover/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../ripple/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../select/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../snippet/package.json Updated framer-motion peer dependency to >=11.0.22.
.../tabs/package.json Updated framer-motion peer dependency to >=11.0.22 and dev dependency to ^11.1.7.
.../tooltip/package.json Updated framer-motion peer dependency to >=11.0.22 and dependency to ^11.1.7.
.../core/system/package.json Updated framer-motion dependency to ^11.1.7.
.../utilities/framer-utils/package.json Updated framer-motion dependency to ^11.1.7.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@wingkwong wingkwong added this to the v2.4.3 milestone Jun 23, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4218335 and b4167eb.

Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
Files selected for processing (17)
  • .changeset/pink-rivers-rush.md (1 hunks)
  • packages/components/accordion/package.json (2 hunks)
  • packages/components/autocomplete/package.json (1 hunks)
  • packages/components/button/package.json (1 hunks)
  • packages/components/calendar/package.json (1 hunks)
  • packages/components/card/package.json (1 hunks)
  • packages/components/dropdown/package.json (2 hunks)
  • packages/components/modal/package.json (2 hunks)
  • packages/components/navbar/package.json (1 hunks)
  • packages/components/popover/package.json (2 hunks)
  • packages/components/ripple/package.json (2 hunks)
  • packages/components/select/package.json (2 hunks)
  • packages/components/snippet/package.json (1 hunks)
  • packages/components/tabs/package.json (2 hunks)
  • packages/components/tooltip/package.json (2 hunks)
  • packages/core/system/package.json (1 hunks)
  • packages/utilities/framer-utils/package.json (1 hunks)
Files skipped from review due to trivial changes (9)
  • .changeset/pink-rivers-rush.md
  • packages/components/button/package.json
  • packages/components/calendar/package.json
  • packages/components/card/package.json
  • packages/components/navbar/package.json
  • packages/components/select/package.json
  • packages/components/snippet/package.json
  • packages/core/system/package.json
  • packages/utilities/framer-utils/package.json
Additional comments not posted (15)
packages/components/ripple/package.json (2)

39-39: Updated framer-motion in peerDependencies to >=11.0.22: This change is consistent with the PR's objective to update the version due to a bug fix in animations. It ensures that users of this package will have the required version that includes the necessary bug fixes.


51-51: Updated framer-motion in devDependencies to ^11.1.7: This update aligns the development environment with the latest stable release of framer-motion, which likely includes additional fixes and improvements beyond the specific bug fix mentioned in the PR. It's good practice to keep development dependencies up to date.

packages/components/tooltip/package.json (2)

39-39: Updated framer-motion in peerDependencies to >=11.0.22: This change ensures that all consumers of the tooltip component are using a version of framer-motion that includes the critical bug fix. This is crucial for maintaining the integrity and functionality of animations within the tooltip component.


62-62: Updated framer-motion in devDependencies to ^11.1.7: Updating the development dependencies to the latest version helps in testing against the most recent features and bug fixes, ensuring that the tooltip component remains compatible and functional with newer versions of its dependencies.

packages/components/dropdown/package.json (2)

39-39: Updated framer-motion in peerDependencies to >=11.0.22: This update is critical for ensuring that the dropdown component works seamlessly with the latest animation features provided by framer-motion, especially since it likely involves dynamic display and hiding of elements.


64-64: Updated framer-motion in devDependencies to ^11.1.7: Keeping the development environment updated with the latest versions of dependencies is essential for catching potential integration issues early in the development cycle. This change helps achieve that goal.

packages/components/popover/package.json (2)

39-39: Updated framer-motion in peerDependencies to >=11.0.22: Ensuring that the popover component, which likely relies heavily on animations for displaying overlays, uses an updated version of framer-motion is crucial for the smooth functioning of these animations.


66-66: Updated framer-motion in devDependencies to ^11.1.7: This ensures that the development tests and builds are performed against the latest stable version of framer-motion, which supports the most recent bug fixes and features.

packages/components/modal/package.json (2)

39-39: Updated framer-motion in peerDependencies to >=11.0.22: The modal component, often involving animations for opening and closing, requires a robust animation library. This update guarantees that the necessary fixes in framer-motion are available to all consumers of the modal component.


67-67: Updated framer-motion in devDependencies to ^11.1.7: Consistency in development dependencies ensures that developers are working with the most up-to-date versions, which can help prevent issues during development and testing phases.

packages/components/tabs/package.json (2)

39-39: Updated framer-motion in peerDependencies to >=11.0.22: For a component like tabs, which may involve transitions between tab content, it is essential to use an animation library that is free from critical bugs. This update ensures such reliability.


62-62: Updated framer-motion in devDependencies to ^11.1.7: This update aligns the development dependencies with the latest stable version of framer-motion, facilitating the development and testing processes with the most recent enhancements and fixes.

packages/components/accordion/package.json (2)

45-45: Approved version update in peerDependencies.

The update to framer-motion in peerDependencies is aligned with the PR objectives and correctly formatted.


72-72: Approved version update in devDependencies.

The update to framer-motion in devDependencies ensures that the latest stable version is used, which is consistent with the PR objectives.

packages/components/autocomplete/package.json (1)

39-39: Approved version update in peerDependencies.

The update to framer-motion in peerDependencies for the autocomplete component is consistent with the other package updates and addresses the bug fix mentioned in the PR description.

@jrgarciadev
Copy link
Member

@wingkwong moving this to v2.5.0 since it might break some users' app

@jrgarciadev jrgarciadev modified the milestones: v2.4.3, v2.5.0 Jun 25, 2024
@wingkwong wingkwong changed the base branch from canary to refactor/framer-motion June 30, 2024 05:20
@wingkwong wingkwong merged commit 25c3510 into refactor/framer-motion Jun 30, 2024
8 checks passed
@wingkwong wingkwong deleted the chore/eng-1044 branch June 30, 2024 05:20
wingkwong added a commit that referenced this pull request Jul 4, 2024
* refactor(ripple): load domAnimation dynamically

* refactor(modal): load domAnimation dynamically

* refactor(accordion): load domAnimation dynamically

* refactor(ripple): rename domAnimation

* refactor(popover): load domAnimation dynamically

* refactor(popover): load domAnimation dynamically

* refactor(tooltip): load domAnimation dynamically

* refactor(navbar): load domAnimation dynamically

* refactor(tabs): load domAnimation dynamically

* refactor(tabs): import only needed

* refactor(navbar): load domAnimation dynamically

* refactor(calendar): load domAnimation dynamically

* refactor(components): revise extension

* fix(modal): add content to memo dependency

* refactor(accordion): move domAnimation outside AccordionItem

* refactor(calendar): move domAnimation outside

* refactor(components): move domAnimation outside

* fix(navbar): remove duplicate definition

* feat(utilities): @nextui-org/dom-animation

* chore(deps): add @nextui-org/dom-animation package

* chore: remove individual domAnimation

* refactor(components): use @nextui-org/dom-animation instead

* fix(navbar): remove duplicate definition

* feat(changeset): add changeset

* fix(tabs): use domMax instead

* chore(deps): pnpm-lock.yaml

* fix(tabs): discard dynamic load for domMax

* chore(deps): framer-motion versions (#3308)

* chore(deps): update framer-motion version in peerDependencies

* chore(deps): sync framer-motion version across packages

* chore(deps): pnpm-lock.yaml

* feat(changeset): add changeset

* chore(deps): sync framer-motion versions

* refactor(tabs): add comments

* chore(changeset): remove tabs
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