$ the-wire · showcase
QUIC stream data survives late readers, fromWeb writes keep async context
By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology
Node fixed two stream-layer data-loss and context-leak classes today, while the dependency bots moved perfetto, simdjson, and V8 forward a notch.
quic: retain readers for readable streams nodejs/node
When a peer-initiated unidirectional QUIC stream sent data and FIN before the consumer made its first async iterator pull, the native stream could be torn down before any reader existed, and the buffered data was gone by the time JavaScript asked for it. The fix constructs the reader when the readable QuicStream is created, so the underlying queue stays alive until the consumer pulls.
stream: keep async context of fromWeb writes nodejs/node
Since the direct-dispatch change to WritableStream writes, fromWeb() had two async-context leaks: a write issued before the stream started ran the sink in the context of the code that created the WritableStream, not the writer. Writable.fromWeb() and Duplex.fromWeb() now preserve the async context of the write across both cases.
deps: patch V8 to 15.6.75.33 nodejs/node
An automated patch update moves V8 to 15.6.75.33. A patch-level V8 bump carries the upstream fixes with it; nothing in the change alters the public API.
meta: skip auto-PR workflows on forks (#1233) nodejs/doc-kit
doc-kit's auto-PR workflows now skip forks, so contributors working from a fork stop tripping automation that assumed a branch in the main repo.
deps: update perfetto to 59.1 nodejs/node
The bots also pulled perfetto to 59.1 and simdjson to 5.1.0, both automated dependency updates with no API surface of their own.
