fix(deps): Remove framer-motion#651
Merged
rebeccaalpert merged 1 commit intopatternfly:mainfrom Aug 18, 2025
Merged
Conversation
|
Preview: https://chatbot-pr-chatbot-651.surge.sh A11y report: https://chatbot-pr-chatbot-651-a11y.surge.sh |
fa9424b to
6c6d7bf
Compare
Framer-motion requires React 18 or higher - we should be able to diy our own solution here instead of relying on it.
nicolethoen
approved these changes
Aug 13, 2025
thatblindgeye
approved these changes
Aug 13, 2025
|
🎉 This PR is included in version 6.4.0-prerelease.13 🎉 The release is available on: Your semantic-release bot 📦🚀 |
rebeccaalpert
added a commit
to rebeccaalpert/virtual-assistant
that referenced
this pull request
Oct 24, 2025
Framer-motion requires React 18 or higher - we should be able to diy our own solution here instead of relying on it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We want to drop framer-motion since it doesn't support React 17 (required by OpenShift). While framer-motion dependency can be replaced easily with a lower version, it may have compatibility issues with 18 and 19. It is probably better to just drop it and diy our own solution here.