Fix: add "use client" directive to feature animation files #3355
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
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.
Continues #3353 #3327
When
LazyMotionuses feature animation files(domAnimation,domMax,domMin), functions are passed asrendererwhich can cause errors in RSC. so, I add"use client"directive to feature animation files to resolve error.As a result,
motion/react-mcan now be used in RSC environments.While I attempted various approaches to make
motion/reactwork as well, unlike other packages that use pre-created elements from client-boundary,motion.divfrommotion/reactappears to dynamically createVisualElement using Proxy. Therefore,motionfrommotion/reactalways requires"use client"directive, so no additional work was done for it.