chore: update to node 22

[snowystinger]

Closes

You might notice that @react-aria/ssr still declares

  "engines": {
    "node": ">= 12"
  },

We can't update this without it no longer handling optional chaining, which webpack 4 cannot handle. So it remains at 12 for everyone and our code transpiles larger. 🤷🏻‍♂️

There is also now a deprecation warning for punycode, this will eventually go away most likely when storybook upgrade is complete and whenever we finally axe lerna.

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

[rspbot]

Build successful! 🎉

• View the storybook
• View the storybook-19
• View the storybook-17
• View the storybook-16
• View the S2 storybook
• View the documentation

The base branch was changed.

[rspbot]

Build successful! 🎉

• View the storybook
• View the storybook-19
• View the storybook-17
• View the storybook-16
• View the S2 storybook
• View the documentation

[rspbot]

Build successful! 🎉

• View the storybook
• View the storybook-19
• View the storybook-17
• View the storybook-16
• View the S2 storybook
• View the documentation

[nwidynski]

@snowystinger Btw, shouldn't the .nvmrc contain 22.x instead of 22.*? I don't think the star syntax is actually valid.

[snowystinger]

@nwidynski doesn't look like it

nvm use
Found '...react-spectrum/.nvmrc' with version <22.*>
Now using node v22.13.1 (npm v10.9.2)

vs

nvm use
Found '...react-spectrum/.nvmrc' with version <22.x>
N/A: version "22.x -> N/A" is not yet installed.

You need to run "nvm install 22.x" to install it before using it.

nvm install 22.x
Version '22.x' not found - try `nvm ls-remote` to browse available versions.

It doesn't actually seem to specify either syntax here https://github.com/nvm-sh/nvm?tab=readme-ov-file#nvmrc
but probably grabbed the star syntax from the lts/* example

Here's what their help says as well

Note: <version> refers to any version-like string nvm understands. This includes:
  - full or partial version numbers, starting with an optional "v" (0.10, v0.1.2, v1)
  - default (built-in) aliases: node, stable, unstable, iojs, system
  - custom aliases you define with `nvm alias foo`

Are you running into an issue using the current entry? or where are you coming up with the x syntax?

[nwidynski]

@snowystinger Meh, apparently both are valid, but even nvm isn't so sure https://github.com/nvm-sh/nvm?tab=readme-ov-file#set-default-node-version:~:text=the%20latest%20installed-,v18.x,-version%20of%20node themselves. I'm a bit surprised nvm install fails with .x syntax 😓

Im currently experiencing trouble with 20.* on supposedly .nvmrc compatible tooling, e.g. mise-en-place. The NPM examples also only mention .x syntax for minor versions 🤷 Regardless, I guess let's take the origin of .nvmrc as source of truth and just keep it that way.

[snowystinger]

It looks like we don't actually need star syntax, we could just use the number 22. Would that work with mise-en-place?

[nwidynski]

@snowystinger Yes 👍

[snowystinger]

#8210