[Question] Should `engines.node` be bumped to 20+?

[spanishpear]

👋 Hello!

I noticed the README currently states:

Currently, Node 18+ is supported. We support the LTS versions of Node. You can add the node package to your CLI to ensure users are running a specific version of Node.

However, node18 is no longer LTS (ended 27 Mar 2025) https://endoflife.date/nodejs

Q) Would you accept a PR to update the relevant configs/CI/docs to upgrade to node 20 (EOL - 30 Apr 2026), or maybe even node22?

Node 20 (EOL - 30 Apr 2026) brings a backported require(esm) support 🥳
Node 22 (EOL - 30 Apr 2027) introduces --experimental-strip-types (the default in 23/24), which could have some performance opportunities 👀

Let me know what you think!

[mdonnalley]

@spanishpear Thanks for bringing this up - this is definitely something we need to address at some point. That said, we're currently swamped with other priorities through November, so we won’t be able to give this the attention it deserves until then.

Even if you're able to take on the work of updating this repo (which we’d really appreciate!), it would require a major version bump. That, in turn, means we’d need to update all of the oclif and Salesforce plugins - about 50 in total - to use the new major version. While the work isn’t massive, it does require coordination and time we just don’t have right now.

Also, since this would be a major release, we’d want to take the opportunity to evaluate any other potential breaking changes - which we unfortunately don’t have the capacity to do at the moment either.

[git2gus]

This issue has been linked to a new work item: W-18738721