Support rendering @motionone/solid
components
#5233
Merged
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.
Changes
Fix #4652
@motionone/solid
components export a proxy component forMotion
, so when you doMotion.div
, it renders adiv
dynamically. The proxy captures the"div"
(or anything) dynamically to render the right HTML element.This brings many issues for Astro:
await Motion
returnsundefined
, because it's akin toMotion.then
and there's no promise to resolve.Motion[Symbol.for('astro:renderer)]
throws because the Proxy doesn't return the right value.Motion.isAstroComponentFactory
is truthy because it returns a Solid component.This PR handles these 3 edge cases to properly handle it. Another solution is to not have
Motion
wrap a Proxy, and follow styled-components' method of a hardcoded list of dom elements.Testing
Added test to
solid-component
Docs
N/A. bug fix.