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

NODE INSPECTOR BUG CRUSHES ABSOLUTE URLS. LLHTTP BUMPED. UNDICI TIGHTENS HTTP/2 PERFORMANCE

By RepoJournal · Filed · About Node.js

A network inspector bug that mangled absolute URLs in HTTP requests is now fixed, while llhttp gets a maintenance bump and Undici optimizes its HTTP/2 client with authority caching.

The inspector was doubling up on URLs when clients passed absolute paths instead of relative ones [1], creating malformed request logs like `http://hosthttp://host/path` — a trap for anyone debugging network traffic in production. The fix handles absolute URLs directly while preserving backward compatibility for relative paths [3]. Separately, llhttp shipped a patch update to 9.4.1 [2], landing upstream in Node with the usual automated dependency sync. Over in Undici, two separate performance wins landed back-to-back: HTTP/2 authority values are now cached to avoid redundant string construction [4], and duplicate request stream setup logic collapsed into a single path [5]. The Node-API CTS gained test coverage for SharedArrayBuffer [6], bridging a gap between the test suite and the compatibility standard. Nothing here demands an emergency patch, but the inspector fix closes a real debugging footgun.

Action items

References

  1. [1] inspector: fix absolute URLs in network http ↗ nodejs/node
  2. [2] deps: update llhttp to 9.4.1 ↗ nodejs/node
  3. [3] inspector: fix absolute URLs in network http nodejs/node
  4. [4] perf(client): cache HTTP/2 authority ↗ nodejs/undici
  5. [5] chore(http2): collapse duplicate request stream setup ↗ nodejs/undici
  6. [6] port test_sharedarraybuffer to CTS ↗ nodejs/node-api-cts

FAQ

What changed in Node.js on May 3, 2026?
A network inspector bug that mangled absolute URLs in HTTP requests is now fixed, while llhttp gets a maintenance bump and Undici optimizes its HTTP/2 client with authority caching.
What should Node.js teams do about it?
Review the inspector fix [ref:1] before next release if you ship network debugging tooling • Undici users: upgrade when convenient for HTTP/2 performance gains
Which Node.js repositories shipped on May 3, 2026?
nodejs/node, nodejs/undici, nodejs/node-api-cts

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.