solidjs / solid / 41590596183

78%

main: 89%

push

github

fix(signals): a pending error-boundary output read only behind fallbacks holds nothing (#4638) (#4639)

* fix(signals): a pending error-boundary output read only behind fallbacks holds nothing (#4638)

Two sibling `<Loading on={sel()}>` boundaries, one reading its async through
an error boundary built in the component body: after a `sel` write neither
showed its fallback. The error boundary's output passes the pending by (A6)
and is a CONFIG_REDERIVE frame reader in `blocked`; it is created outside the
Loading, so `hiddenBy` never saw the fallback its only reader is behind, and
it held the transaction the sibling's forwarded pending opened. A boundary
output is transparent: hidden when every reader of it is (F-4, D-14).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE

* test(web): import createErrorBoundary from solid-js/internal in the #4638 spec

The public entry keeps createErrorBoundary @internal, so its types live on
solid-js/internal; the type-check step failed with TS2305.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE

* perf(signals): hiddenBy walks readers with a while loop (-13 B minified)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0117BoWNSSgtemsSYsaX2hXE

---------

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

803 of 1104 branches covered (72.74%)

Branch coverage included in aggregate %.

1131 of 1369 relevant lines covered (82.62%)

29.93 hits per line