fix(enterprise): remove deferStream to fix share page hydration mismatch #5511
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
deferStream: truefrom share page route to fix blank page issue with large session dataProblem
Share pages with large data (3.5MB+) render as completely blank pages. The
$Rhydration promises never resolve, leaving#appwith only a Solid marker comment.Observed behavior:
#app innerHTML:<!--!$e000000010000000020000000010-->(empty)$Robject: 790 keys loaded, butR[0], R[3], R[5]stuck as unresolved promisesRoot Cause
deferStream: truewas added in commit 95526fb (Dec 11, 2025) with the intent to fix share image meta tags. However, this causes streaming chunk processing failures with large payloads:Solution
Remove
deferStream: trueto ensure data is embedded in initial HTML rather than streamed. This guarantees hydration completes regardless of payload size.OG Image Impact: None (No Regression)
Removing
deferStreamdoes not affect OG images because they are already broken in production:Why OG tags don't work (regardless of deferStream):
The
<Meta property="og:image">tag is inside<Show when={data()}>:Since
<head>is sent beforedata()resolves, OG meta tags are never included in the initial HTML response. This is a separate issue that requires moving meta tags outside of<Show>.Testing
Related
🤖 GENERATED WITH ASSISTANCE OF OhMyOpenCode