Node.js Technical Steering Committee member Matteo Collina has proposed adding a first-class Virtual File System (VFS) to Node.js core, raising both technical and philosophical questions about AI-assisted development in critical infrastructure.
Matteo Collina, Node.js Technical Steering Committee member and co-founder of Platformatic, has submitted a significant proposal to add a Virtual File System (VFS) to Node.js core through a new node:vfs module. The proposal, documented as PR #61478 on the Node.js GitHub repository, introduces approximately 19,000 lines of code across 100 files and has ignited substantial community discussion. The conversation extends beyond the technical merits of the feature itself, touching on the controversial fact that the implementation was largely built using Claude Code, an AI coding assistant.
The Technical Proposal
Node.js has always centered its identity around I/O operations, 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 scenarios by providing an in-memory, fs-compatible API with mount points, overlay mode, symlinks, and module loading hooks.
The implementation introduces a virtual layer above the actual file system, allowing developers to work with files that exist entirely in memory. This approach offers several advantages:
Performance: Eliminating disk I/O can dramatically speed up operations, especially in testing scenarios. As one developer noted on Hacker News, "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."
Security: Sandboxing file access becomes more straightforward, which is particularly valuable in multi-tenant environments where isolation is critical.
AI Integration: The VFS provides a natural way to handle AI-generated code without the overhead of writing temporary files to disk. As developer Jake Morrison commented, "I've been writing generated code to temp files and then cleaning up after and it always felt wrong. Keeping it in memory and importing directly makes so much more sense."
Implementation and Adoption
Alongside the core proposal, Platformatic has released @platformatic/vfs as a userland package on npm, available immediately 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: swapping '@platformatic/vfs' for 'node:vfs'.
The VFS concept has gained traction across the JavaScript ecosystem. Vercel has independently extracted the same API into its own node-vfs-polyfill package, while LangChain has already adopted VFS for agent sandboxing through @langchain/node-vfs.
The AI Contribution Debate
Collina was transparent about the development process, stating that the implementation was built with significant AI assistance over Christmas 2025. He explained that he "pointed the AI at the tedious parts" while focusing on architecture, API design, and reviewing every line of code. This approach has sparked a broader debate about the role of AI in open-source development, particularly in critical infrastructure projects.
In response, Fedor Indutny, a long-time Node.js core contributor known for initiating the io.js fork, launched a petition on GitHub calling for AI-generated code to be disallowed in Node.js core. The petition argues that the scale of the PR raises concerns around the Developer Certificate of Origin (DCO) and the ability of reviewers to adequately verify machine-generated code.
On Reddit, Indutny wrote: "I firmly believe that the critical infrastructure Node.js is, is not the place for such changes." This perspective has divided the community, with some developers expressing concern about the implications of AI-generated code in core infrastructure, while others defend the approach when guided by experienced maintainers.
As one Hacker News commenter noted: "if there's anyone I would trust in exploring these avenues, it's him and the maintainers doing god's work in the Node.js repo in these past few years."
Ecosystem Response
Neither Bun nor Deno currently offer an equivalent built-in VFS. Deno has already opened issue #32783 to track adding node:vfs compatibility. Bun, which leads benchmarks in raw file system throughput, has not announced comparable plans.
The Node.js Technical Steering Committee is expected to vote on policies governing AI-assisted contributions, which will determine the fate of the PR. This vote could set a precedent for how AI-generated code is treated across the broader open-source ecosystem.
Documentation and Migration
Developers interested in exploring the VFS implementation can find documentation for the userland package and migration path on the Platformatic blog and the @platformatic/vfs GitHub repository.
The proposal represents a significant evolution in Node.js architecture, potentially changing how developers interact with file systems in the runtime. Whether through the core implementation or userland packages, the Virtual File System concept appears poised to address longstanding challenges in JavaScript development, particularly as AI-generated code becomes more prevalent.
Comments
Please log in or register to join the discussion