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 FIXES STORAGE CRASH AND FFI VALIDATION BUG

By RepoJournal · Filed · About Node.js

Node core landed critical fixes for a Storage.prototype length crash and FFI void parameter validation, while undici realigned its lifecycle with bundled Node versions.

The most pressing fix arrives in src: a crash when reading length on Storage.prototype [1] is now resolved, preventing crashes in production code that touches the Storage API. Alongside that, the FFI layer now properly validates 'void' as a parameter type in getFunction and getFunctions [2], closing a gap where invalid void parameters could slip past validation. A secondary issue in ContextifyContext property definer interception is also fixed [3], preventing double invocation of definer callbacks on writable properties. On the documentation front, fs.StatFs got a comprehensive overhaul with expanded descriptions, byte-count examples, and clarification on units [4], making it actually useful for developers. Undici aligned its end-of-life timeline to match the Node version it's bundled in [5], so if you're tracking bundled dependencies, your EOL calendar just got cleaner. The doc tooling got a minor bump [6] that keeps the pipeline stable.

Action items

References

  1. [1] src: fix crash when reading length on Storage.prototype nodejs/node
  2. [2] ffi: validate 'void' as parameter type in getFunction and getFunctions nodejs/node
  3. [3] src: fix ContextifyContext property definer interception result ↗ nodejs/node
  4. [4] doc: improve fs.StatFs documentation with examples and clarifications ↗ nodejs/node
  5. [5] docs: match undici EoL to node version it's bundled in ↗ nodejs/undici
  6. [6] tools: bump @node-core/doc-kit from 1.3.5 to 1.3.6 in /tools/doc in the doc group ↗ nodejs/node

FAQ

What changed in Node.js on May 28, 2026?
Node core landed critical fixes for a Storage.prototype length crash and FFI void parameter validation, while undici realigned its lifecycle with bundled Node versions.
What should Node.js teams do about it?
Pull the Storage.prototype and FFI fixes into your next Node patch release • Review fs.StatFs examples in the updated docs for your storage handling code • Sync undici EOL dates with your Node version tracking
Which Node.js repositories shipped on May 28, 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.