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 SHIPS STREAM FLUSH FIX AND EXPERIMENTAL VFS SUBSYSTEM

By RepoJournal · Filed · About Node.js

A critical stream transform bug that broke consecutive stateless pipelines is now fixed, and Node is adding a virtualized filesystem layer for the first time.

The stream fix [1] resolves a flushing bug where stateless transforms in a chain weren't receiving their own final null signals after upstream data arrived during flush. This broke pipelines that relied on precise stream lifecycle semantics. Separately, Node's landing an experimental `node:vfs` subsystem [2] with memory and real filesystem providers, though filesystem module integration is coming in follow-up PRs. On the testing front, the coverage API now works with `isolation: 'none'` [3], fixing a bootstrap gap where V8 coverage wasn't enabled for non-isolated test runs. The crypto subsystem also got a cleanup [4]: WebCrypto methods are no longer async wrappers, routing through a shared validation helper that converts errors to rejected promises while letting internal implementations return native job promises directly.

Action items

References

  1. [1] stream: flush each fused stateless transform ↗ nodejs/node
  2. [2] vfs: add minimal node:vfs subsystem ↗ nodejs/node
  3. [3] test_runner: support coverage with isolation:'none' via run() API ↗ nodejs/node
  4. [4] crypto: remove async from WebCrypto methods nodejs/node

FAQ

What changed in Node.js on May 24, 2026?
A critical stream transform bug that broke consecutive stateless pipelines is now fixed, and Node is adding a virtualized filesystem layer for the first time.
What should Node.js teams do about it?
Apply stream flush fix if you use stateless transforms in pipelines • Review `node:vfs` experimental API if building custom filesystem layers • Test coverage reports with `run({ coverage: true, isolation: 'none' })`
Which Node.js repositories shipped on May 24, 2026?
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.