Node.js: Stream Stall Fixes and Test Runner Polish

Merged fixes for HTTP drain stalls and web streams pipe races address production reliability hangs and crashes. A cluster of open test runner proposals and routine npm and undici updates round out the day.

Duration: PT2M28S

Episode overview

This episode is a short developer briefing from Node.js.

It explains recent repository work in plain language.

  • Show: Node.js
  • Published: 2026-11-07T14:04:30Z
  • Audio duration: PT2M28S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it is Saturday, November 7th, 2026, and this is your Node.js briefing.

The top signal today is reliability in core streaming paths, with two merged fixes for hangs and hard crashes developers could hit in production.

First, HTTP responses could stall after flushing buffered writes. Since chunked writes were coalesced while auto-corked, backpressure is tracked on buffered bytes, but the underlying socket measures multi-byte text differently. With non-ASCII content completing asynchronously, the drain signal was never sent,…

Related, web streams piping could throw an internal assertion. A slow-path write is deferred to a microtask, and if the pipe shut down and released its writer in between, the deferred write found no stream. PR 63733 now skips that write when shutdown has started.

Second theme is test runner polish. Four open proposals tighten edge cases that cause silent skips, hangs, or wrong timing. That includes treating a falsy skip option as not skipped in PR 67313, fixing mock property restore for getter properties like file system promises in PR 67310, setting mocked timers to each…

Finally, routine dependency movement: automated updates landed npm to version…

Nearby episodes from Node.js

  1. Filesystem and HTTP/2 Stability Fixes
  2. Startup Speed Push and Certificate Check Fix
  3. Weekly Recap - Startup Speed and Network Reliability
  4. Memory Retention Fixes and API Correctness
  5. Reliability Hardening and Hot-Path Speedups
  6. Dependency Sweep and Runtime Reliability Fixes
  7. X.509 Upgrades and HTTP Reliability
  8. HTTP2 Cleanup, FFI Fixes, and Build Efficiency