RepoJournal
Node.js

@nodejs

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

Pick a date

  1. Tue 5 may
  2. Wed 6 may
  3. Thu 7 may
  4. Fri 8 may
  5. Sat 9 may
  6. Sun 10 may
  7. Mon 11 may
  8. Tue 12 may
  9. Wed 13 may
  10. Thu 14 may
  11. Fri 15 may
  12. Sat 16 may
  13. Sun 17 may
  14. Mon 18 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

UNDICI 8.2.0 SHIPS WITH WASM FIX AND HTTP/2 BODY HANDLING IMPROVEMENTS

By RepoJournal · Filed · About Node.js

Undici's latest release addresses critical HTTP/2 body transmission bugs while Node core continues refactoring its profiling and debugger infrastructure for maintainability.

Undici v8.2.0 [1] dropped overnight with fixes for HTTP/2 body handling on non-expectsPayload methods and corrected the WASM SIMD environment variable logic that was blocking optimization paths. The release also switches to native addAbortListener instead of polyfilling, reducing surface area. In parallel, Undici's pool management got tighter [2] [3]: stale client replacement now respects connection limits while preserving pool capacity, preventing resource leaks in long-lived services. The dispatcher selection in BalancedPool [4] also shed redundant scans — targeted cleanup for high-throughput scenarios. On the Node core desk, the team is systematically refactoring for clarity: profiling helpers split from util into dedicated files [5], debugger components moved to separate modules [6], and FFI's DynamicLibrary now protected against premature garbage collection [7]. Temporal also joined the frozen intrinsics list [8]. Meanwhile, the CI infrastructure migration from JSON-based OpenSSL matrix to Nix definitions [9] provides cleaner variation handling for future patching scenarios.

Action items

References

  1. [1] v8.2.0 ↗ nodejs/undici
  2. [2] fix: replace stale pool clients under connection limit ↗ nodejs/undici
  3. [3] fix: preserve pool capacity after removing stale client ↗ nodejs/undici
  4. [4] perf: avoid redundant scans in BalancedPool dispatcher selection ↗ nodejs/undici
  5. [5] src: split profiling helpers from util ↗ nodejs/node
  6. [6] debugger: move ProbeInspectorSession and helpers to separate files ↗ nodejs/node
  7. [7] ffi: prevent premature GC of DynamicLibrary nodejs/node
  8. [8] lib: add Temporal to frozen intrinsics nodejs/node
  9. [9] tools: migrate from `openssl-matrix.json` to `openssl-matrix.nix` ↗ nodejs/node

FAQ

What changed in Node.js on May 2, 2026?
Undici's latest release addresses critical HTTP/2 body transmission bugs while Node core continues refactoring its profiling and debugger infrastructure for maintainability.
What should Node.js teams do about it?
Upgrade Undici to 8.2.0 if you run HTTP/2 workloads or use long-lived pools • Verify UNDICI_NO_WASM_SIMD environment variable not misconfigured in production • Watch for Node core refactors landing; no breaking changes yet but internal API surface shifting
Which Node.js repositories shipped on May 2, 2026?
nodejs/undici, nodejs/node

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.