Skip to content

Commit c0789ed

Browse files
committed
Merge next into fix/adoption-lazy-child-pairing-3712
Re-base the size caps this PR raises on next @ 49a765c, which now carries #3993 (store snapshot on structural writes) and #3992 (once-per-show fallback): + createStore, hydrating + every store family, compiled CSR and compiled hydrating. Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_018LY7F9czoRqdMEvk2QwPr1
2 parents b7ece8c + 49a765c commit c0789ed

135 files changed

Lines changed: 3460 additions & 2025 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/signals": patch
3+
---
4+
5+
A boundary's fallback is instantiated once per show. An `<Errored>` whose content reads a failing async memo through a `<Show>` rendered its fallback twice for one failure and rebuilt it when a `reset()` retry failed again, losing focus on the Retry button (#3991). The fallback is now built in a scope of its own beside the boundary's output and kept while it shows; a later error reaches it through the error accessor. The same holds for a `<Loading>` fallback across the boundary's re-derives.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/diagnostics": patch
3+
---
4+
5+
The browser bridge keeps shared references in the payload it transfers. `toSerializable` treated every object it had already written as a cycle and dropped it, so a `LONG_HOLD` diagnostic, whose `data` carries the hold's own `blockers` and `acknowledgements` arrays, left the hold record in `attribution.holds` without them, and `expectNoSilentHolds` threw a `TypeError` on any browser capture that recorded a long hold. The serializer now tracks only the ancestors of the value being written: an object reached twice is written twice, and only an object that contains itself is dropped.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"solid-js": patch
3+
---
4+
5+
A rejection contained by `<Errored>` is no longer reported as unhandled when the boundary shares a `{props.children}` slot with an async sibling during SSR (#3973). While its holes were pending, the server boundary threw a combined promise that the slot retry could drop, so its rejection exited Node even though the fallback rendered. The combined promise is now marked handled where it is created; anything that awaits it still sees the rejection.
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
"@solidjs/web": patch
3+
---
4+
5+
A server component that throws during its synchronous render is no longer cacheable. `respond(View, { headers })` puts those headers on the frame response, and the response is a 200 whose body carries the error, so an author's `cache-control: public, max-age` stored the failure. When the render fails before the head is built, the frame response sends `Cache-Control: no-store` and drops the CDN-targeted fields that would override it at a CDN (`CDN-Cache-Control`, `<CDN>-CDN-Cache-Control`, `Surrogate-Control`). The status stays 200 and the body still carries the error record. A render that succeeds keeps the author's headers, and so does a returned `{ error }` value: the author chose that value and the headers that travel with it. A failure that lands after a suspended shell has already left can no longer change the head.
6+
7+
`@solidjs/web/frames/server` no longer exports `renderServerComponent`, `renderToFrameStream`, `serverComponentResponse` or `createFrameSink`. They were internal building blocks: a server component reaches the client by being returned from a server function (directly or wrapped in `respond()`), and the transform hooks (`frameTransformResult`, `frameTransformFlightResult`, `frameTransformDirectResult`) render and frame it. The entry is experimental, and the hooks and document-shell exports are unchanged.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/signals": patch
3+
---
4+
5+
Attribution: `GRAPH_GROWTH` no longer counts the previous route's computations when a navigation settles through a held transition (#3989). The navigation record still settles in the landing, but its graph walk waits for that drain's end, after the landing's commits dispose the page left — the same instant a one-drain navigation is counted. Observe tier only; no production bytes.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/compiler": patch
3+
---
4+
5+
The native compiler no longer drops a component `ref` whose value is wrapped in a TypeScript `as` cast, non-null `!` or `satisfies`, such as `ref={[setRef, props.ref] as any}`; it classified the wrapper instead of the value inside and emitted no `ref` prop. The universal generate also keeps array refs on components and unwraps `as` and `!` on element refs, so `<view ref={myRef as any} />` assigns the element to `myRef`, as the Babel plugin does.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/web": patch
3+
---
4+
5+
A synchronous `prepareRequest` hook no longer defers the server-function request by a microtask, so reads adopted during hydration stay inside the hydration trace instead of refetching from the browser (#3959). An async hook is still awaited.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"solid-js": patch
3+
---
4+
5+
On the server, a render effect's retry and a projection's re-derive (`createProjection`, `createStore(fn)`, `createOptimisticStore(fn)`) run under their own render's context once a pending source settles, as an async memo's retry already does (#3972). Under concurrent requests they ran under whichever render set the context last, so anything the pass created took the other request's hydration ids.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
"@solidjs/signals": patch
3+
---
4+
5+
A structural store write during hydration's snapshot capture (a row removed from an array from `onSettled`, by `splice` or `reconcile`) records the container's pre-write backing as its snapshot, the way a leaf write already does. Readers inside the snapshot scope, such as a hydrated `<For>`, are held on the server's list until the scope is released instead of re-running mid-claim against a snapshot `length` and live items, which rendered a row for `undefined`, threw, and halted reactivity (#3950). A record with more than 32 keys commits such a write to a copy of its backing, so the recorded snapshot keeps the pre-write key set for a scoped reader created after the flush.

0 commit comments

Comments
 (0)