129 wires and counting

$ follow Node.js

Keep up with Node.js in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-05
stories 70

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

STREAMS SHED ALLOCATIONS, HTTP/2 WINDOWS QUADRUPLE

By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology

Node.js core cut per-chunk memory overhead in pipeTo by eliminating redundant promise allocations, while HTTP/2 default window sizes jumped 64x to unlock full bandwidth on high-latency connections.

The streams team shipped a major optimization [1] that eliminates the write request records and microtask closures Node.js was creating for every single chunk flowing through pipeTo. The improvement directly unlocks throughput on high-latency networks. Separately, HTTP/2 stream windows jumped from 64KB to 4MB and connection windows to 32MB [2], which the maintainers calculated will deliver 16MB/s (128Mbps) on the stream window instead of 256KB/s on a 250ms RTT connection. The FFI subsystem gained a significant speedup [3] by reusing libffi 3.7's precomputed call plans for fixed-signature functions on x86-64, falling back gracefully on older versions. Test infrastructure got leaner [4] by switching SQLite tests to in-memory databases where filesystem persistence wasn't needed. On the documentation front, doc-kit underwent a major modularization [5] [6] [7], splitting the core engine (now @nodejs/doc-kit at 1.0.0) from Node-specific and legacy generators into separate npm packages with optional peer dependencies.

Action items

References

  1. [1] stream: cut per-chunk allocations in pipeTo ↗ nodejs/node
  2. [2] http2: increase default window sizes ↗ nodejs/node
  3. [3] ffi: reuse libffi call plans ↗ nodejs/node
  4. [4] test: prefer in-memory databases in sqlite tests ↗ nodejs/node
  5. [5] refactor(node): extract @node-core/doc-kit package, move core to @nodejs/doc-kit ↗ nodejs/doc-kit
  6. [6] refactor(legacy): extract @nodejs/doc-kit-generator-legacy package ↗ nodejs/doc-kit
  7. [7] refactor(react): extract @nodejs/doc-kit-generator-react package ↗ nodejs/doc-kit

Quick answers

What shipped in Node.js on August 5, 2026?
Node.js core cut per-chunk memory overhead in pipeTo by eliminating redundant promise allocations, while HTTP/2 default window sizes jumped 64x to unlock full bandwidth on high-latency connections. In total, 37 commits and 33 pull requests landed.
Who contributed to Node.js on August 5, 2026?
8 developers shipped this update, including mcollina, Antoine du Hamel, Paul Bouchon, umuoy1, avivkeller, btea, Trott, and Node.js GitHub Bot.
What were the notable Node.js updates?
stream: cut per-chunk allocations in pipeTo, http2: increase default window sizes, and ffi: reuse libffi call plans.