RepoJournal
Node.js

@nodejs

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

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

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

NODE CORE LANDS PERFORMANCE WINS ACROSS NET, FS, AND STREAMS

By RepoJournal · Filed · About Node.js

BlockList gets a comprehensive performance overhaul, Windows file handles gain native support, and stream abort logic finally passes spec.

James Snell shipped a sweeping optimization to net.BlockList [1] that eliminates shared pointers, adds read/write locking, introduces bulk address operations, and includes a new clear method, addressing both correctness and speed across the entire API. Windows developers now have a path forward: a new windowsHandle option on fs.createReadStream() and fs.createWriteStream() [2] wraps raw Win32 HANDLEs through CRT file descriptors, fixing the EBADF failures that plagued inherited pipe handles from other processes. The streams implementation fixed a critical recursive abort bug [3] by rechecking stream state after signaling abort, as the spec requires, finally passing WPT and removing its expected-failure entry. Separately, zlib tightened ZIP parsing by rejecting ambiguous EOCD records [4], scanning candidates in a consistent tail window to prevent trailing padding from changing which central directory gets used. Buffer allocation gains optional alignment support [5], letting you allocate 4096-byte aligned buffers for direct file I/O without wrapper overhead. On the infrastructure side, docker-node switched to consuming dist/index.json for version resolution [6], simplifying the release pipeline and removing HTML parsing fragility [7].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] net: improve performance of net.BlockList nodejs/node
  2. [2] fs: add windowsHandle option to file streams ↗ nodejs/node
  3. [3] stream: fix recursive WritableStream abort nodejs/node
  4. [4] zlib: reject ambiguous ZIP archive ends ↗ nodejs/node
  5. [5] buffer: support aligned allocations ↗ nodejs/node
  6. [6] chore: consume dist/index.json when resolving versions ↗ nodejs/docker-node
  7. [7] chore: consume dist/index.json when resolving versions (#2598) nodejs/docker-node

Quick answers

What shipped in Node.js on August 7, 2026?
BlockList gets a comprehensive performance overhaul, Windows file handles gain native support, and stream abort logic finally passes spec. In total, 15 commits and 15 pull requests landed.
Who contributed to Node.js on August 7, 2026?
7 developers shipped this update, including MattIPv4, James M Snell, PickBas, Jeong SeokChan, mcollina, ronag, and avivkeller.
What were the notable Node.js updates?
net: improve performance of net.BlockList, fs: add windowsHandle option to file streams, and stream: fix recursive WritableStream abort.

More from @nodejs

Daily updates, in your inbox

Follow Node.js

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

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?