[robertjchen]

Details

Bumps Node to 24.22.1, which rejects TLS chains through the eight compromised eMudhra intermediate CAs (nodejs/node#66871). Node uses its own compiled-in root store, so OS ca-certificates updates don't cover it.

Related Issues

For https://github.com/Expensify/Expensify/issues/693812

Manual Tests

1. Run nvm install and confirm node -v prints v24.22.1.
2. Run node -e 'fetch("https://dv-g3b-emudhra.we-have-a-problem.com/").then(r=>console.log(r.status)).catch(e=>console.log(e.cause?.code))'.
3. Confirm it prints CERT_REVOKED.

Linked PRs

N/A

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[robertjchen]

I have read the CLA Document and I hereby sign the CLA

[JakubKorytko]

Tested locally and looks good, thanks a lot!

Note

No action needed from library consumers. .nvmrc isn't included in the published package, and devEngines is only enforced for the root project, so npm ignores it when the library is installed as a dependency. Apps using @expensify/react-native-wallet keep using their own Node version.

[os-botify]

🚀 Published to npm in 0.2.1 🎉