solidjs / solid / 36063911976

74%

main: 89%

push

github

fix(web): frames server build shares one server-functions instance; X-Frame-Stream carries the invocation id (#3641) (#3643)

The frames server artifacts bundled a private copy of the server-function
runtime, so the invocation ledger the handler wrote was never the one
frameTransformFlightResult read: every single-flight server-component
response left with X-Frame-Stream "" and the client rendered nothing.
Resolve the sink's server-function, wire-layer and SSR-runtime imports to
the public entries (one instance per app by construction, as #3640 did
for the client half). Externalizing the SSR runtime also fixes <select
value> inside a server component: compiled output armed the select-value
gate through @solidjs/web and the bundled renderer copy never saw it.

Dist-level spec against the built artifacts in all three tiers; frames
server artifact 155 KB -> 44 KB.

Co-authored-by: Claude via Cursor <noreply@cursor.com>

606 of 894 branches covered (67.79%)

Branch coverage included in aggregate %.

883 of 1142 relevant lines covered (77.32%)

25.03 hits per line