Migrate to motion and refactor codebase
#184
Merged
Conversation
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
Temzasse
force-pushed
the
feat/migrate-to-motion
branch
from
82c849d to
2dc3bf2
Compare
Temzasse
force-pushed
the
feat/migrate-to-motion
branch
from
2dc3bf2 to
b8466d4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Now that I found some time during Christmas holidays I tried to tackle multiple issues at once 🎅🏻🎄
The main thing that this PR does is migrate the library from
framer-motiontomotion(see new Motion docs here). Another substantial change is updating the library and all examples to target React 19.Other changes are more quality of life changes of smaller bug fixes discovered while refactoring the codebase.