Remove yarn v1 from Node 26? #88
Description
I'm raising this as we're looking at removing yarn from the images produced by the docker-node project (@nodejs/docker team) and only shipping with npm which would be consistent with what is in the base node.js tarballs.
While the docker group has had several discussions on this in the past there are a few reasons to consider it now:
- Yarn v1 has not been receiving updates for some time now
- including yarn is a difference from what is included in the tarballs
- Most Linux distributions don't automatically include yarn (in fact npm is also separate in most) so it's not clear that it makes sense to include it by default as there perhaps shouldn't be that expectation from end users.
- Changing it in node 26 but leaving it in earlier versions should be a "safe" time to make such a change.
- I feel yarn is not as popular as it used to be when some of the issues were discussed previously in the docker-node group in 2000
Interested to have a conversation around this and hear people's thoughts. I note that we don't have a specific group who look at this sort of thing (what's included in distributions from the nodejs org) although we do have a @nodejs/distros and @nodejs/delivery-channels teams but they're not quite focussed on whether things like this should be added on. Perhaps another team to look at consistency of this sort of thing across delivery channels would be useful.
Throwing all of this out for discussion :-)