perf(nuxt): prevent head dom from rendering twice #22974
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
β Type of change
π Description
With the move to immediately rendering the dom instead of debouncing it, we've introduced a regression in that the head will render to the DOM twice.
While the performance impact of this is reduced by quite a bit with Unhead 1.3, it's still not ideal and maybe adding ~5ms of extra load time.
The underlying issue is that we should wait for the suspense to resolve if we know the app is hydrating.
π Checklist