Node.js: TLS Internals Reused for QUIC, and a Wave of Filesystem Edge-Case Fixes

The biggest change today is architectural — QUIC now reuses the generic TLS pause mechanism from PR #65522, simplifying 0RTT handling — while a cluster of smaller fixes tightens up filesystem, test-runner, and crypto edge cases across the board.

Duration: PT2M41S

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-09-02T13:06:42Z
  • Audio duration: PT2M41S

Transcript excerpt

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

Good day, this is your Node.js briefing for September 2nd, 2026.

The standout change today is architectural. Tim Perry's PR 65522 takes the TLS pause machinery originally built in PR 64827 and generalizes it so QUIC can reuse it directly. Instead of QUIC deferring events with custom machinery, handshakes now pause, and resume, using the same mechanism as regular TLS. The…

Second theme: a steady stream of filesystem correctness fixes. PR 65713 lets `cp` and `cpSync` accept Buffer paths, matching behavior elsewhere in the `fs` module. PR 65731 fixes a regression where `cpSync` with dereference enabled wasn't dereferencing symlinks nested inside copied trees. And PR 65736 catches a real…

Third theme: flaky and incorrect test infrastructure getting cleaned up. PR 65672 fixes WASI poll timing tests that could misfire on wall-clock boundaries. PR 65728 deflakes test runner coverage by refreshing temp directories between subtests. And PR 65739 fixes worker ID reuse in the test runner — IDs were being…

Worth flagging individually: PR 65520 fixes a live lock between environments in the Web Locks manager, where two environments could wake each other forever without progress. And two backport…

Wh…

Nearby episodes from Node.js

  1. Chasing Down Correctness Bugs in Certs, Watchers, and Isolates
  2. Virtual File Systems Move Toward Production
  3. Weekly Recap - Concurrency Fixes and New Module Surfaces
  4. Crypto Correctness and Streams Cleanup
  5. Cleaning Up After Fast Follows
  6. SQLite Reentrancy Bugs and a Wave of Security Hardening
  7. Closing the Gaps in Streams, Crypto, and Cleanup Order
  8. Crypto Gets a Major Overhaul