Support vinext SSR stream bootstrap#9
Draft
southpolesteve wants to merge 1 commit intoTanStack:mainfrom
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
bootstrapScriptContentsupport to the server stream options and emit escaped inline bootstrap scripts.<!DOCTYPE html><html>, moving those tags into the existing<head>.Why
vinext App Router SSR uses Vite RSC output. The browser entry is provided to the HTML renderer as inline bootstrap script content, matching React DOM's
bootstrapScriptContentoption. Without this, the server HTML can render but the vinext client runtime does not start.The same flow can suspend at the root while the RSC stream is resolved. In React, this is allowed; in Redact, the root throw escaped because there is no Suspense boundary above it. vinext needs Redact to await and retry the shell without leaking the aborted render's partial chunks.
The document-shell normalization covers React 19-style metadata projection that vinext/Next-compatible app trees can produce, where head tags may appear before the document root in the render tree but must land inside
<head>in HTML.Validation
pnpm --filter tests test -- ssr