fix(nuxt): remove experimental hash hydration #22648
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.
π Linked issue
Related #22620
β Type of change
π Description
Doing some testing on Nuxt production environments, I believe the HashHydrationPlugin is not ready to be used.
There is an internal issue in Unhead on how non-hydrated dom nodes won't be removed. For users who opt-in and are aware of the constraint it shouldn't be an issue, but for something that we're planning to be enabled by default, I don't think it's worth including it while the issue is present.
Also, it does increase the INP time slightly for page changes so may not be worth it for the performance hit there.
π Checklist