Scope

Upgrade Node.js runtime version to 22

Potential Risks / Drawbacks

• Unknown / un-identified breaking changes between Node.js versions
• People that are running the raw Node process somewhere somehow will have to upgrade
  • That might be an issue depending on your host, though Node 22 came out in April so you'd hope enough time has gone by for hosts to upgrade their stack

Review Notes / Questions

• It's another game of What is a breaking change? As far as I can tell, Node 22 is backwards compatible with 18 so no breaks there, though there's always the chance of weirdness with external modules.
  • ✅ It's not breaking for Docker users per se, it's a potential breaking for raw-process and non-sandboxed extensions users. This is mentioned in the breaking changes docs pages.
• Isolated-vm might have some wonkiness. I remember that being a thing last time we checked
  • ✅ Confirmed that the "snapshot" issue is not affecting us. Other issues with newer Node.js versions seem to be solved as well in the latest isolated-vm version. Tested on AMD and ARM. We therefore go without the --no-node-snapshot Node.js flag as this would come with unnecessary start-up time / performance degradation.
• Do we want to make 22+ required, or keep 18+ as the requirement and allow 22? The latter makes it not a breaking change at the downside that we're now technically supporting 3 major versions of the runtime
  • ✅ Making 22+ required as keeping it on 18+ would prevent us from being able to use new 22 features and keeping dependencies up-to-date which have dropped support for < 22 as well. The complexity of supporting too many different Node.js runtime versions at the same time would therefore come with a certain reduction in quality.

Fixes #22124