docs(cloudflare): correct over-claim on client hydration - #38
Merged
Conversation
The Next 15 .js manifest fix (#30) wires the client reference manifest that was previously null — a real, general bug. But I marked "client hydration resolved" before browser-validating, which was premature: the manifest is necessary plumbing, not a guarantee an app hydrates. In practice a browser "client-side exception" is usually the app's own client code — most often a NEXT_PUBLIC_* / auth env var missing at build time (inlined into the client bundle), so a provider throws on hydration. The deploy serves the HTML + chunks + RSC Flight payload correctly. Reframe the doc: manifest plumbing is wired; full hydration also depends on the app's client config. Add a troubleshooting note. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Reconcile the hydration-claim correction with main's v0.14+ status text: keep main's factual detail (URL-decoded R2 asset keys #34 + Next 14/15 client- reference-manifest reading, plus the client-side-exception debug note) while applying the correction — the plumbing being wired does NOT mean hydration is "done"; App Router pages still render a blank shell until the SSR gap lands. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ru3K1fyNRnyTXQ95Gmv6Su
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.
CLOUDFLARE_PARITY.mdclaimed client-component hydration was "resolved (v0.14+)"and listed
"use client"interactivity as production-ready. That over-claims:the manifest + chunk-loading plumbing is wired (and the
ChunkLoadErrorR2-keydecode bug from #34 is fixed), but App Router pages still render a blank shell
until the SSR runtime gap closes — hydration is not guaranteed by the plumbing
alone.
This corrects the intro, the capability table, and the status section to say
"plumbing wired, hydration not "done"" while preserving the factual fix detail
and the client-side-exception debug note. Docs-only.
🤖 Generated with Claude Code
https://claude.ai/code/session_01Ru3K1fyNRnyTXQ95Gmv6Su