No AI in Node.js Core
porsager
49 points
28 comments
March 19, 2026
Related Discussions
Found 5 related stories in 57.3ms across 3,471 title embeddings via pgvector HNSW
- Petition to Node.js TSC: No AI Code in Node.js Core indutny · 11 pts · March 18, 2026 · 73% similar
- Why No AI Games? pavel_lishin · 67 pts · March 03, 2026 · 56% similar
- Ask HN: Looking for programmers who don't use and don't want to use AI Eliah_Lakhin · 11 pts · March 25, 2026 · 52% similar
- Show HN: I built an OS that is pure AI evanbarke · 18 pts · March 28, 2026 · 52% similar
- AI is making junior devs useless beabetterdev · 162 pts · March 01, 2026 · 51% similar
Discussion Highlights (9 comments)
ramesh31
This is a silly reactionary response. Where is the line? Can I use AI to look up APIs? Write documentation? What if I write a function and ask AI to test it? What if I manually implemented an idea that I thought about after chatting with AI a few weeks ago? Stop treating this like it's going to go away. We need actual solutions for the FOSS community that make reviewing AI assisted work tractable.
ronsor
Related: https://news.ycombinator.com/item?id=47413195 @indutny explains their views in that thread.
tylerchilds
On the one hand, agreed On the other hand, I haven’t and I believe many of us, have never paid node any money so it feels weird to dictate their approach.
cj
I have no unique perspective to add other than an obvious question: If the PR is low quality, why not just close/reject it? Does it matter if it's AI assisted or not?
graphememes
Honestly, this is a small pebble but feels like a ripple in the reasons why node.js is losing to bun and others.
cpursley
If they allow AI in Node it just might do a full rewrite into Rust, Go or Elixir ;)
pan69
> A 19k lines-of-code Pull Request was opened in January, 2026. Such a PR should be rejected simply because of the shear size of it, regardless of AI use. Seriously, who submits a 19k line PR? Just make many small ones.
vova_hn2
I don't see, how such policies can possibly achieve more good, then harm. A person, who posts slop for whatever reason, or runs bots that post slop, will simply ignore them. An honest person, who cares about the quality of their contribution and genuinely wants to improve the project will be more limited in the choice of tools to do so. So, this policy only serves to limit honest contributors, while doing absolutely nothing to stop spammers/slopposters.
rglover
I can see the good intention in this move, but it's not realistic. The genie isn't going back in the bottle, so the priority shouldn't be artificial limits, but more emphasis on review and sets of eyes required to sign off on a merge.