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.
One email a day. Unsubscribe in one click.
Keep up with Node.js in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Apply stream flush fix if you use stateless transforms in pipelines nodejs/node [plan]
- → Review `node:vfs` experimental API if building custom filesystem layers nodejs/node [monitor]
- → Test coverage reports with `run({ coverage: true, isolation: 'none' })` nodejs/node [plan]
References
- [1] stream: flush each fused stateless transform ↗ nodejs/node
- [2] vfs: add minimal node:vfs subsystem ↗ nodejs/node
- [3] test_runner: support coverage with isolation:'none' via run() API ↗ nodejs/node
- [4] crypto: remove async from WebCrypto methods nodejs/node