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-07-19
stories 13

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

NODE FIXES CRITICAL STREAM PIPE BUG BLOCKING HEALTHY DESTINATIONS

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

A regression in Node's stream handling silences data flow to working destinations when a sibling pipe errors, breaking multi-destination pipelines across all recent versions.

Node shipped a critical fix for stream piping [1] that restores flow to healthy destinations when one errored destination is removed. The bug, introduced in v20.10.0 [2], caused sources piped to multiple destinations to stall completely if any single destination errored synchronously in _write(). This breaks common patterns like splitting data across multiple processors. The fix ensures the source's drain handler is re-invoked even when the destination no longer has needDrain set, properly cleaning up the errored destination from awaitDrainWriters. In parallel, Node's REPL is getting a major overhaul to use the inspector protocol instead of vm [3], closing multiple longstanding issues around REPL behavior and debugger integration. The team also patched assert.deepStrictEqual and util.isDeepStrictEqual [4] to handle Maps with null keys correctly, which previously threw TypeErrors instead of returning comparison results. Documentation improvements continue landing, including a comprehensive doc-kit documentation site [5] that showcases the tool itself and serves as a web example for the broader ecosystem.

Quick answers

What shipped in Node.js on July 19, 2026?
A regression in Node's stream handling silences data flow to working destinations when a sibling pipe errors, breaking multi-destination pipelines across all recent versions. In total, 8 commits and 5 pull requests landed.
Who contributed to Node.js on July 19, 2026?
6 developers shipped this update, including bmuenzenmeyer, Mahin Anowar, avivkeller, Paul Bouchon, greenhead, and Node.js GitHub Bot.
What were the notable Node.js updates?
stream: resume flow when an errored pipe destination is removed, stream: resume flow when an errored pipe destination is removed, and repl: use inspector over vm.