Repository navigation
Dropping old Node support #40
Description
I know this is breaking so it may be something you want to kick down the line until you have other things that are also breaking. It would be great to drop support for Node 18, and 20 (or increase the minor) as then you could replace picocolors with node:util styleText and enquirer and nanospinner with @clack/prompts, that would clean up the dependency graph a little (although already looking small, so no rush :D) and improve performance.
Feel free to close this though if you want to revisit later, but also good be good for tracking 🙏
Activity
ghostdevv commentedon May 30, 2026
Just noticed on an old project that is on Node 18 actions-up doesn't work as cac requires Node >=20.19
azat-io commentedon Jun 15, 2026
Thank you for your issue!
Thank you for bringing the latest update to the cac package to our attention. I have restored support for Node.js v18 by removing the package
We should give some thought to the discontinuation of support for Node.js v18 and weigh up the pros and cons. At present, it seems to me that this version is still widely used.
mrjones-plip commentedon Jun 15, 2026
Node 18 is EOL well over a year ago. For that matter, Node 19, 20 and 21 are EOL too. 22 is the next LTS that's still getting updates and if yer gonna bump from 18, I suggest going to a supported LTS. Checking stats, it looks 18 is still for sure being downloaded, but 22 and 24 have had a serious uptick in the past 12mo.
A bit off-topic, but maybe a docker version
actions-upwould bypass all the OS level node dependencies? You could bind mount the repo you're operating on so it could make the updates? This way any node dependencies are entirely encapsulated in the docker image and there's no bare OS dependencies.