deps: bump node to v22.16.0

[JonasBa]

v24 is the new LTS https://nodejs.org/en/blog/release/v24.0.0
v22 is still LTS until 2025-10-28

getsentry: https://github.com/getsentry/getsentry/pull/17678

[JonasBa]

@joshuarli what is the process for updating the mirror and shasum? I've updated the shasum to match the files available from node, but I'm currently getting a 404 from our mirror

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[joshuarli]

i've updated this PR to use .node-version!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@             Coverage Diff             @@
##           master   #93080       +/-   ##
===========================================
+ Coverage   52.96%   87.26%   +34.30%     
===========================================
  Files       10278    10331       +53     
  Lines      592704   593213      +509     
  Branches    23026    22956       -70     
===========================================
+ Hits       313919   517691   +203772     
+ Misses     278353    75086   -203267     
- Partials      432      436        +4     

[natemoo-re]

I'm working on the CI failures—just a resolution issue with a node-style specifier in the rspack config.

[natemoo-re]

Unfortunately had to roll Node back because v24.x does not start active LTS until 2025-10-28. Vercel only supports active LTS (which is the correct thing to do, of course).

Bumping from v22.11.0 to v22.16.0 will unlock require(esm) without a flag, which is what we need for some upcoming rspack dependencies to work.

[joshuarli]

Unfortunately had to roll Node back because v24.x does not start active LTS until 2025-10-28. Vercel only supports active LTS (which is the correct thing to do, of course).

Bumping from v22.11.0 to v22.16.0 will unlock require(esm) without a flag, which is what we need for some upcoming rspack dependencies to work.

sounds good - i'll update our mirrors

[scttcper]

vercel doesn't matter tbh. but fine either way

[scttcper]

oh nvm i get it, vercel would need the unflagged transpile. got it

[natemoo-re]

True! Just being cautious of the official guidance since bugs on Current releases aren't unheard of.

Production applications should only use Active LTS or Maintenance LTS releases.

And yeah, Vercel doesn't expose v24 yet for that reason.