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.

@nodejs

The Node.js runtime — every backend team's CVE source of truth

github ↗

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

NODE FIXES CRITICAL STREAM PIPE BUG BLOCKING HEALTHY DESTINATIONS

By RepoJournal · Filed 06:56 UTC on July 19, 2026 · About Node.js

6 people shipped this

Mahin Anowar @MahinAnowar 2 cited

bmuenzenmeyer @bmuenzenmeyer 1 cited

avivkeller @avivkeller 1 cited

Paul Bouchon @bitpshr 1 cited

greenhead @greenheadHQ

Node.js GitHub Bot @nodejs-github-bot

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.

Action items

→ If you pipe to multiple destinations, upgrade to the latest patch immediately nodejs/node [immediate]
→ Review any assertions comparing Maps with null keys - behavior now consistent nodejs/node [plan]
→ Test REPL and debugging workflows after inspector protocol migration lands nodejs/node [monitor]

References

[1] stream: resume flow when an errored pipe destination is removed nodejs/node
[2] stream: resume flow when an errored pipe destination is removed ↗ nodejs/node
[3] repl: use inspector over vm nodejs/node
[4] assert,util: fix TypeError on Maps with null keys nodejs/node
[5] feat(docs): add documentation for `doc-kit` ↗ nodejs/doc-kit

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.

HTTP2 HEAP-USE-AFTER-FREE FIX LANDS IN NODE CORE

Node shipped a critical fix for a heap-use-after-free vulnerability in HTTP/2 stream handling that could crash servers under specific receive-and-send patterns.

javascript 20 shipped 1-min read

@nodejs 2 days ago

NODE SITE BANNERS NOW DISMISSIBLE

The nodejs.org homepage got a close button, letting visitors dismiss the banner instead of living with it forever.

javascript 3 shipped 1-min read

@nodejs 3 days ago

NODE STREAM VALIDATION FIX LANDS, NIGHTLY BUILDS ROLL

Stream writer methods now properly validate options.signal before use, closing a gap where invalid signals caused inconsistent behavior across push, broadcast, and fromWritable.

javascript 25 shipped 1-min read

@nodejs 4 days ago

NODE.JS RELIABILITY REPORT LOGGED FOR MID-2026

A reliability report has been added to the Node.js tracking system for July 15, 2026, though details remain sparse at this early stage.

javascript 1 shipped 1-min read

— or follow the whole beat:

Elsewhere on the wire

@cachyos about 10 hours ago

CACHYOS LINUX 7.1.4 SHIPS WITH SCHEDULER REVERT AND AMD AUDIO FIXES

The kernel bumped to 7.1.4 overnight with a critical scheduler revert and targeted audio driver fixes for AMD systems.

infra 57 shipped 1-min read

Elixir & Phoenix about 10 hours ago

ECTO FIXES SILENT DATA CORRUPTION IN MAP UPDATES AND BELONGS_TO LOOKUPS

Two critical Ecto bugs that silently corrupt changeset data are now fixed, and you should merge these immediately if you're using map or association updates.

elixir 10 shipped 1-min read

Mobile platforms about 10 hours ago

SWIFT COMPILER DROPS DECADE-OLD INTEROP WORKAROUND, REIMPLEMENTS CORE OPTIMIZER IN PURE SWIFT

Swift's ClangImporter finally stopped stripping type aliases that have been unnecessary since 2014, while the compiler's foundational SSAUpdater moved entirely off C++ dependencies.

mobile 28 shipped 1-min read

@dotnet about 10 hours ago

SOURCE.DOT.NET PROXY LAYER BROKEN, SOURCEBROWSER GETS MAJOR OVERHAUL

source.dot.net is serving HTTP 500s and stale assets because the proxy layer exposes bugs that local-disk deployments never catch, and SourceBrowser just got a significant upgrade that's likely its last.

dotnet 12 shipped 1-min read