-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: React - Use "createRoot" instead of "hydrateRoot" for client:only
#3337
Conversation
🦋 Changeset detectedLatest commit: b04de83 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
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 |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Welp, turns out we can use this from personal testing! Nested component islands and children are just as stable using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Few comments about future-proofing the last argument.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to merge!
…ly` (withastro#3337) * feat: pass "client" directive to clientEntrypoints * refactor: remove hydration warning suppression react 17 * feat: remove hydration warning suppression react 18 * chore: changeset * fix: change metadata to options bag
Changes
client:only
#3010client
directive to client renderersclient.js
to usecreateRoot
onclient:only
instead of suppressing hydration warnings (spoiler: they aren't suppressed!)client-17.js
to userender
onclient:only
instead of suppressing hydration warningsTesting
N/A, check your console 😉
Docs
N/A