“Virtual File System” PR for Node.js comes with a disclaimer:

"Disclaimer: I've used a significant amount of Claude Code tokens to create this PR. I've reviewed all changes myself.”

LoC added: +18945

Thankfully it hasn't been merged yet. The changes are all over the place and this makes me uncomfortable about running Node.js long term.

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

Virtual File System for Node.js by mcollina · Pull Request #61478 · nodejs/node

A first-class virtual file system module (node:vfs) with a provider-based architecture that integrates with Node.js's fs module and module loader. Key Features Provider Architecture - Extensi...

GitHub
My perhaps overly irritated response to the PR: https://github.com/nodejs/node/pull/61478#issuecomment-4075998105
And... this ended with a petition that I want to put before TSC vote in two weeks https://github.com/indutny/no-slop-in-nodejs-core
GitHub - indutny/no-slop-in-nodejs-core: A petition to disallow acceptance of LLM assisted Pull Requests in Node.js core

A petition to disallow acceptance of LLM assisted Pull Requests in Node.js core - indutny/no-slop-in-nodejs-core

GitHub

Update: I'm so proud of y'all!

I know AI companies and many employers aren’t making it easy to step out and say "no" to it, but you went in and signed the petition. I respect that a lot!

We still have time to get more names on the list and make stronger case for TSC committee, but seeing all these names under it is already very refreshing in the days where every news cycle either talks about AI changing the world or about job cuts by major companies (in addition to wars, obviously).

Some people asked me if I could offer a way to sign the petition without having a github account, so I created a mirror (?) on Change.org:

https://www.change.org/p/no-ai-code-in-node-js-core

Github is still a preferred way to sign this, but if for some reason this doesn't work for you - at least now you have an alternative way to make your voice heard!

Sign the Petition

No AI code in Node​.​js Core

Change.org
@indutny is anyone ok to sign? I have never contributed directly to NodeJS. I'm just a user.
@claudius absolutely! As long as you care about it - go for it!

@indutny I'm all for this. And will sign momentarily.

That said, what teeth does this have? Will you be able to present this in the meeting where the vote is held?

@bengl that's my plan! Join the meeting and present this to TSC
@indutny for sure there is the whole license thing, but what triggers me the most is that a complete understanding of the code produced is becoming a secondary thing.

@yasser yes, absolutely!

I’m trying to find a common ground on which we could base the decision not to accept such change, and which is agreeable to engineers leaning on LLMs heavily. DCO seemed like a good starting point since in my reading it clearly is incompatible with the LLM assisted contributions.

@indutny I left my comment on the HN article just now:

> I used Node.js extensively for about a decade, both professionally and as a hobby. I don't buy the problem statement.

> These arguments don't even make sense, they look LLM generated. I can't even formulate a disagreement against this nonsense.

@andrewrk thank you!

There’s now going to be a TSC vote on the matter in about two weeks. I'll hope to present these points succinctly before the committee!

@indutny good luck. is signal built using node.js?
@andrewrk @indutny Just what Signal needs: a virtual filesystem. It's OK everyone, the coder audited it themself, so you know it'll be secure. [thick sarcasm]

@andrewrk tbh, I feel exactly the same about the proposed change itself. It is hard to buy whatever is being sold...

Thankfully the outrage that I felt happened way before I could even take a look at the code. Asking people to review 19k LoC LLM-generated PR is beyond what I'd consider basic politeness. The disproportionality of the time spent implementing this and the time needed to carefully review and catch slop mistakes is egregious.

@indutny there has been so much thought and care poured into node.js over the years... to dilute it feels like spray painting some shitty graffiti on top of a beautiful mural
@andrewrk I think I'm gonna rephrase and use this if you don't mind!
@indutny go for it, I don't even need attribution
@indutny

github.com/nodejs/node/pull/61478#issuecomment-4078275365

Lmao, "we have analyzed ourself and found nothing wrong"
@indutny Honestly not irritated enough. Fuck AI slop. No one should shovel 19k lines of code that they didn't write and probably don't even understand into a project. They need to fuck off and keep fucking off until they figure out what responsible engineering is.

@indutny thanks for challenging this. I agree that the DCO seems largely incompatible with LLM usage it actually read it and think.

Most people haven’t read it or thought about it, just sign off your commit that Claude made and move on.

The LF (sadly) seems to be rather unbothered by it.