$ the-wire · showcase
Workers preload streams into the startup snapshot; http2 accepts repeated content-encoding
By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology
3 people shipped this
Node's startup path got cheaper today: worker stdio streams are built into the snapshot instead of re-initialized on every thread start, and http2 stopped collapsing repeated content-encoding to the first value.
worker: preload streams into startup snapshot nodejs/node
Worker stdio used to load its stream after restoring the main-thread context, initializing the stream constructors and prototype methods on every startup. The stream is now preloaded during snapshot construction so workers restore that initialized state, while worker-specific stdio instances and message ports are still created at runtime; only Readable and Writable stay eager, with operators, p...
http2: preserve multiple content-encoding values nodejs/node
content-encoding was in the single-value field set, so an incoming header with several codings arrived as only the first. It now joins every value in order and accepts outgoing arrays without throwing ERR_HTTP2_HEADER_SINGLE_VALUE by default. This is a behavior change: code that relied on the array being rejected on send will now have it accepted.
perf: let worker.stream take chunks as they arrive nodejs/doc-kit
worker.stream required all of its input before starting any work; it now also takes an async iterable of batches and starts each batch's work as it arrives, with a few chunks per thread in flight and results yielded in submission order. The commit message notes "An input that arrives whole, as it does with one thread, works as before." It is the first part of a stack splitting the larger change.
stream: trim webstreams sink wrappers and BYOB transfers nodejs/node
Round 23 of the webstreams performance series stops wrapping a sink's close and abort and a transformer's flush and cancel in async closures held for the stream's lifetime: two per WritableStream and two per TransformStream, each with its context. The one-shot methods are now stored as-is and called with the spec's argument list.
sea: generate a compile cache for the VFS modules nodejs/node
Single executable applications currently reject "useCodeCache": true alongside "useVfs": true. The PR attributes this to a plumbing gap rather than a V8 limit, since the SEA code cache is only consumed by the embedder compile paths while a VFS main script runs through the regular CJS/ESM loaders. Separately, doc-kit merged the streamed-input half of that stack.
