fix: Nested hydration with Solid

[ryansolid]

Changes

Updated Solid's client renderer and integration to fix issue with nested hydration, like you'd find in the recursive comments in Hackernews.

Previous behavior recreated static children as DOM elements and inserted them during hydration. This reset hydration state messing with Solid's hydration when nested.

Solid treats any undefined value inserted as skip during hydration assuming client will match server eventually, so I just removed the children and it will skip hydration of static children.

This also appears to improve the Solid integration's hydration performance by about 200%.

Testing

Docs

[changeset-bot]

🦋 Changeset detected

Latest commit: a8daed3

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

This PR includes changesets to release 2 packages

Name	Type
@astrojs/solid-js	Patch
@astrojs/renderer-solid	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

[ryansolid]

Woke up and realized I missed a case. I need to update this for when Solid dynamically renders the static children outside of hydration. I will update this PR in a bit.

[ryansolid]

Ok I've made it better now. Took some thinking since we don't really ever want to be creating these nodes on the client if possible. I've tested a number of scenarios. Including children initially being present or not, and eager versus lazy evaluation of children.

[natemoo-re]

This looks amazing, thank you so much @ryansolid! Excited to see what folks can build with this now!