Node.js Virtual File System Proposal Sparks AI Code Debate
Matteo Collina, Node.js Technical Steering Committee member and co-founder of Platformatic, has submitted a proposal to add a built-in Node.js Virtual File System to the runtime’s core. Filed as PR #61478 on GitHub, the proposal introduces roughly 19,000 lines of code across 100 files. It delivers an in-memory, fs-compatible API with mount points, overlay mode, symlinks, and module loading hooks via a new node:vfs module.
The Node.js Virtual File System addresses real pain points developers face today. Running AI-generated code safely, executing tests without hitting the disk, bundling Single Executable Applications, and sandboxing file access in multi-tenant platforms have all historically required workarounds. With node:vfs, those use cases get a clean, native solution.
Alongside the proposal, Platformatic released @platformatic/vfs as a userland npm package, available now for Node.js 22 and above. The API mirrors the proposed core module exactly. When node:vfs ships, migrating will require a single import change. Vercel has also extracted a compatible API into its own node-vfs-polyfill. Meanwhile, LangChain has already adopted the package through @langchain/node-vfs for agent sandboxing.
Developer enthusiasm has been strong. On Hacker News, one user pointed out that tools like Yarn, pnpm, and webpack each had their own workarounds for this problem, and called the standardization long overdue. Another developer on Hashnode described how he had been writing generated code to temp files just to clean them up afterward, calling the in-memory import approach far more sensible.
Still, the PR has become a flashpoint. Collina was transparent that he built the implementation largely with AI assistance over the 2025 Christmas break, focusing on architecture and design while directing the AI at the more tedious parts. In response, long-time core contributor Fedor Indutny, who initiated the io.js fork, launched a petition on GitHub to ban AI-generated code from Node.js core. His concern centers on the Developer Certificate of Origin and whether reviewers can meaningfully verify machine-generated contributions at that scale. On Reddit, Indutny wrote that critical infrastructure like Node.js is not the right place for such changes.
Others disagreed sharply. Several Hacker News commenters argued that Collina’s track record and oversight of every line made the process sound. Neither Bun nor Deno currently offer a built-in equivalent, though Deno has opened issue #32783 to track potential node:vfs compatibility. The Node.js TSC is expected to vote on a policy governing AI-assisted contributions, and that vote will likely decide the proposal’s fate.
