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 LANDS IN NODE CORE WITH HTTP/2 FIX

By RepoJournal · Filed · About Node.js

Node's bundled HTTP client now properly aligns HTTP/2 empty body handling with HTTP/1 semantics, closing a consistency gap that could break streaming assumptions.

Undici 8.2.0 shipped into Node core [1] carrying a critical fix for HTTP/2 content-length behavior on empty bodies [2]. The issue: content-length methods weren't consistent between h1 and h2 protocols, meaning code that worked reliably over HTTP/1 could silently fail over HTTP/2. This is the kind of protocol-level inconsistency that burns hours in production debugging. The undici repo also moved to stop interfering with @types/node type definitions [3], untangling a dependency mess where outdated undici-types were shadowing current implementations. On the Node side, the HTTP module tightened drain event semantics [4] — drain now fires only after socket buffers actually empty, fixing a race condition where 'drain' fired while writableLength remained non-zero. This restores the invariant developers reasonably expect. Meanwhile, armv6 support moved out of experimental [5], and documentation got minor structural cleanup [6].

Action items

References

  1. [1] deps: update undici to 8.2.0 ↗ nodejs/node
  2. [2] fix: align h2 empty body content-length methods with h1 (#5172) nodejs/undici
  3. [3] types: stop interfering with @types/node ↗ nodejs/undici
  4. [4] http: emit 'drain' on OutgoingMessage only after buffers drain nodejs/node
  5. [5] build: remove armv6 from experimental platforms nodejs/node
  6. [6] doc: minor structural stream/iter edits ↗ nodejs/node

FAQ

What changed in Node.js on May 5, 2026?
Node's bundled HTTP client now properly aligns HTTP/2 empty body handling with HTTP/1 semantics, closing a consistency gap that could break streaming assumptions.
What should Node.js teams do about it?
Update to Node with undici 8.2.0 to fix HTTP/2 streaming inconsistencies • Review HTTP drain event handling in streaming code — semantics changed • Verify @types/node compatibility after undici type definition changes
Which Node.js repositories shipped on May 5, 2026?
nodejs/node, nodejs/undici

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.