solidjs / solid / 40286529247

79%

main: 89%

push

github

fix(solid): hydrated Errored boundary runs its content in the hydration pass (#4279)

* fix(solid): hydrated error boundary recovers when its inputs change (#4273)

A boundary hydrated from a serialized error threw that error without
running its content, so it tracked nothing and could only recover through
reset(). It now reads a signal flipped at hydration end, re-running the
content once for real: a client failure keeps the built fallback and
tracks the content's inputs; a server-only error gives way to the
client's content.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

* test(solid): hydrated error boundary holds the client's own error (#4273)

When the content's run at hydration end throws, the boundary holds that
client error: the fallback receives it and reset() clears it. The
serialized server error only directs hydration to claim the fallback.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

* fix(solid): hydrate an errored boundary's content in the pass (#4273)

Replaces the re-run at hydration end. When the server sent an error, the
boundary runs its content in the hydration pass with its data adopted by
id and no DOM claimed under it (`_uc`, read by isClaiming), so nothing
the server answered is fetched again and the fallback claims the
server's markup. A content that fails on the client holds that error and
tracks its inputs. A content that runs clean keeps the server's fallback
and error up behind a hold, ended by reset() or the content re-running.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

* perf(solid): golf the hydrated Errored hold under the size caps (#4273)

Claiming is turned off for the content by a claim window over no owner
(the existing isCla... (continued)

773 of 1068 branches covered (72.38%)

Branch coverage included in aggregate %.

17 of 18 new or added lines in 1 file covered. (94.44%)

1122 of 1366 relevant lines covered (82.14%)

27.66 hits per line