solidjs / solid / 38760169963

78%

main: 89%

push

github

fix(solid): load a streamed fragment's lazy assets before its resume claims it (#4087) (#4093)

A `<Loading>` boundary reads its module map (`<id>_assets`) when it first
evaluates. When its content renders after the shell flushed (a lazy page
behind `<Show>`, or an async manifest resolver), the map ships with the
fragment, after hydration claimed the boundary, so the still-streaming
resume did not wait for the module. The re-run then took the asset-wait
branch and rendered nothing, and that empty render reached the parent's
insert while hydrating and cleared the content the reveal had swapped in:
a "Hydration structure mismatch" and handlers bound to detached nodes.

At the reveal the resume now loads the map the fragment brought and
resumes once its modules land (unchanged when there is none). The map read
moves into one helper, which also drops the `has`/`typeof` checks:
`load` answers `undefined` for a missing key and `loadModuleAssets` loads
nothing for it.


Claude-Session: https://claude.ai/code/session_018fTNh1FgQx2WTF5xoxwML1

Co-authored-by: Claude <noreply@anthropic.com>

751 of 1042 branches covered (72.07%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

1086 of 1328 relevant lines covered (81.78%)

27.81 hits per line