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-09-16
stories 40

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

QUIC no longer reports truncated streams as complete

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

Node's QUIC implementation stopped hiding abrupt stream failures inside otherwise successful reads, and the VFS work closed a cluster of node:fs hooks that misbehaved on mounted paths.

quic: fix readable stream truncation on stop-sending, abort & timeout nodejs/node

by pimterry

Any QUIC stream closed abruptly, by idle timeout, local destroy() or stopSending(), or remote reset, used to surface as a successfully completed stream on the iterable, truncating data without notice; the stream now reports the abort instead of a clean end. The PR describes the current behavior plainly: "we still exposed the data as a successfully completed stream on the iterable". Code that re...

vfs: fs hook gaps nodejs/node

by pipobscure

Several node:fs entry points behaved differently for a mounted path than a real one because of how the call reaches the VFS hooks: fs.watchFile and fs.promises.watch threw a TypeError on handler methods that do not exist, fs.watch on a nonexistent mounted path returned a polling watcher instead of ENOENT and kept the process alive, and fs.utimesSync and fs.readdirSync were also affected. This c...

tools: use self-repository references nodejs/node

by Filip Skokan

Local actions and reusable workflows in nodejs/node now resolve from the running workflow commit via $/ references, independent of checkout paths. The tarball job's action-only checkout and the WPT action checkout/copy workaround were both removed as no longer needed.

test: deflake util.throttle tests nodejs/node

by panva

The util.throttle tests were deflaked by moving timing assertions into a separate test with mocked timers and a matching libuv clock, covering both punctual and delayed dispatch; short windows could expire between synchronous calls when the process was descheduled, and delayed timer dispatch could release two queued calls together and break the spacing assertion.

chore(release): 5.0.5 [skip ci] nodejs/changelog-maker

by semantic-release-bot

changelog-maker 5.0.5 landed with a js-yaml bump from 4.3.1 to 4.3.2, and nodejs-dist-indexer shipped 1.8.27 with the same js-yaml 4.3.1 to 4.3.2 change on its dev dependency; otherwise a quiet day, with googletest updated in nodejs/node to 8eff9e336692fc95961e096564f1044c600b881d and the reliability report for 2026-09-16 filed.

Quick answers

What shipped in Node.js on September 16, 2026?
Node's QUIC implementation stopped hiding abrupt stream failures inside otherwise successful reads, and the VFS work closed a cluster of node:fs hooks that misbehaved on mounted paths. In total, 23 commits, 15 pull requests, and 2 releases landed.
Who contributed to Node.js on September 16, 2026?
5 developers shipped this update, including Filip Skokan, pipobscure, nodejs-github-bot, pimterry, and semantic-release-bot.
What were the notable Node.js updates?
quic: fix readable stream truncation on stop-sending, abort & timeout, vfs: fs hook gaps, and tools: use self-repository references.