Should AI‑Generated Code Be Banned from Node.js Core? Inside the 19k‑Line PR Controversy

Background

In early 2026, a petition signed by over a hundred developers called on the Node.js Technical Steering Committee (TSC) to prohibit AI‑generated code from being merged into the core repository.

Claude‑generated VFS pull request

Node.js TSC member and Fastify maintainer Matteo Collina submitted pull request #61478 that adds a virtual file system (VFS) module ( node:vfs) to Node.js. The PR touches roughly 19 000 lines of code across 80 files (about 14 000 lines of actual implementation). Collina disclosed in the PR description that the majority of the code was produced with Claude Code , an Anthropic AI programming tool, and that he personally reviewed every change.

The VFS aims to solve several long‑standing limitations of the built‑in fs module:

Packaging applications as a single executable without bundling external resources.

Providing an in‑memory file system that integrates with the module resolver, enabling import() to work transparently.

Isolating multi‑tenant environments by avoiding path‑based security checks.

Allowing dynamic code generation without relying on temporary files on disk.

Existing solutions such as memfs and unionfs only patch the fs API and cannot be fully integrated into the module loading pipeline.

Review process and community reaction

The PR triggered an intensive review cycle: 128 review attempts and 108 comments were logged by March 26 2026, and the changes remained unmerged.

The petition against AI‑generated contributions lists three core concerns:

Ethics : Large language models are trained on data that may include copyrighted or unlicensed code, raising legal and moral issues.

Education : Relying on AI can impede learning for new contributors, reducing long‑term sustainability of the project.

Privilege : Access to advanced AI tools often requires paid subscriptions or substantial hardware, creating barriers for reviewers who must reproduce and verify the changes.

Signatories include former TSC member Fedor Indutny , JavaScript author Kyle Simpson , and Zig Software Foundation chair Andrew Kelley .

Node.js TSC response

The TSC plans to vote on disclosure and attribution guidelines for AI‑assisted contributions. The proposed policy would require contributors to explicitly state AI involvement and retain full responsibility for the code, while allowing responsible use of AI to accelerate development.

Contrast with the Linux kernel community

At the same time, the Linux kernel community reported a rapid improvement in AI‑generated contributions. Kernel maintainer Greg Kroah‑Hartman demonstrated that a simple prompt could generate 60 suggested patches, of which two‑thirds were directly applicable after minimal manual refinement. This shift turned earlier “AI slop” (low‑quality, noisy reports) into high‑value bug fixes and suggestions.

Linux projects now label AI‑assisted patches with a “co‑develop” tag and use AI primarily as a code‑review assistant, though the line between assistance and authorship is blurring.

Key references

GitHub pull request: https://github.com/nodejs/node/pull/61478

Petition repository: https://github.com/indutny/no-ai-in-nodejs-core

Discussion on Reddit: https://www.reddit.com/r/javascript/comments/1rz2pc6/petition_no_ai_code_in_nodejs_core/

Greg Kroah‑Hartman interview (The Register): https://www.theregister.com/2026/03/26/greg_kroahhartman_ai_kernel/