You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit adb1efc
Browse filesBrowse the repository at this point in the historyBrowse files
Resolves the conflict with #4154 (e4edd34), which replaced the FrameChunk
union with record-batch FrameMessages. The observe-tier `startedAt` moves
onto FrameMessage's `start` variant (the one non-record message that opens
a flight), and FrameHost.apply reads it from `msg` when the `start` opens
the store. The landing stamp and the transport's header-time `start` carry
over unchanged; all of it stays behind `_SOLID_OBSERVE_`, so prod bytes are
unchanged.
The #4140 spec's fetch stub now writes the wire as record batches
(`{ id, version, r }`) instead of the removed `html` / `complete` chunks.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2
Async-mode renders (`await renderToStream(...)`) now produce the same bytes for the same data, whatever order the async sources settle in (#4028). Once the thenable is taken, hydration writes and the pending-promise stub batch are held until the serializer flush and handed to seroval sorted by hydration key, so reference ids and resolution chunks no longer follow settle order. A body-digest ETag now matches across renders whose only difference was API latency. Streaming consumers (`pipe` / `pipeTo` / `readable`) and custom serializers/sinks are unchanged.
Frames: the frame stream now carries versioned batches of keyed records (`{ id, version, r }`), the same writes the client's resident store applies, instead of eleven typed chunks the client translated into records. The server writes records natively: `renderServerComponent`, `renderToFrameStream` and the response helpers pipe these wire messages, so there is one format from the producer to the store. Records written in the same synchronous flush leave as one message per frame (a segment's assets, content and reveal travel together; a sweep stays one batch), with nothing held across a flush. Only `start`, `data` and the single-flight `outcome` keep a `type`, and the document face's live channel carries the same batches. The eager frames client loses its translation step (about 0.2 KB brotli off every server-components page). Experimental wire format: a client and server must come from the same release.
Fix the tokenizer treating the first attribute of a dynamic tag as its tag name. `<${Comp} title="...">` or `<${Comp} style=${...}>` entered raw text mode, so the children were read as text and parsing failed with "Unclosed tag".
EFFECT_RELAY_TEAR no longer flags effects that measure layout. When the effect's apply half takes no argument (`createEffect(open, () => setFlipped(measure()))`), a write that equals the compute output is not a copy, and its tears stay advisory however often they repeat. Effects whose apply half takes the value are judged as before, so boolean mirrors still warn.
0 commit comments