Node.js centers on I/O primitives like streams, buffers, sockets, and files, but several workflows have required workarounds. Running AI-generated code, executing tests without touching disk, bundling Single Executable Applications, and sandboxing file access in multi-tenant platforms are targeted by a proposed virtual file system. The node:vfs module would provide an in-memory, fs-compatible API with mount points, overlay mode, symlinks, and module loading hooks. Platformatic also released @platformatic/vfs for Node.js 22+, mirroring the proposed core API and enabling a one-line migration to node:vfs. Vercel created a node-vfs-polyfill with the same API, and LangChain adopted VFS for agent sandboxing.
"Node.js has always centred its identity around I/O, with streams, buffers, sockets and files forming the backbone of the runtime. However, common workflows such as running AI-generated code, executing tests without touching the disk, bundling Single Executable Applications (SEAs) and sandboxing file access in multi-tenant platforms have historically required workarounds. The proposed node:vfs module aims to address all four by providing an in-memory, fs-compatible API with mount points, overlay mode, symlinks and module loading hooks."
"Alongside the core proposal, Platformatic has released @platformatic/vfs as a userland package on npm, available today for Node.js 22 and above. The package mirrors the API proposed for core, and when node:vfs ships, migrating is a one-line import change: swap '@platformatic/vfs' for 'node:vfs'. Vercel has independently extracted the same API into its own node-vfs-polyfill package, and LangChain has already adopted VFS for agent sandboxing through @langchain/node-vfs."
"On Hacker News, one commenter noted that: Yarn, pnpm, webpack all have solutions for this. Great to see this becoming a standard. I have a project that is severely handicapped due to FS. Running 13k tests takes 40 minutes where a virtual file system that Node would just work with it would cut the run time to 3 minutes."
Read at InfoQ
Unable to calculate read time
Collection
[
|
...
]