legacy nodejs compatibility: getRandomBytes

[legobeat]

• fix: support randomBytes for older Node.js versions
  • crypto.getRandomValues is only available on Node.js versions v17+.
  • crypto.randomBytes provides the same API as randomBytes, with the same randomness guarantees as crypto.getRandomValues.
  • This makes the implementation runtime compatible with Node.js v12 and v14.
• github ci: add supported nodejs v16 to test matrix
  • Adds coverage for already supported version
• github ci: add legacy nodejs v14 to test matrix
  • Figuring that even if it's not officially supported, it could be relevant to monitor compatibility in CI?
  • v12 is not compatible with the used version of typescript so can not build.

---

Related

• meta: Indicate compatible Node.js versions noble-curves#152

[paulmillr]

V16 is also not officially supported by node. Only v18 is

[legobeat]

V16 is also not officially supported by node. Only v18 is

For sure! But that's a different question to which versions can be used with @noble/hashes right?

(BTW: For example Debian still maintains security updates down to v12, even actively supported Ubuntu 20.04 LTS is still on v10. Enterprise Linux vendors like RedHat and SUSE also typically provide support for older versions regardless of upstream maintainer schedules. So continued use of older Node.js majors beyond the official support windows is not necessarily deprecated per se)

[paulmillr]

I think we can support any version/platform which is not pain in the ass. E.g. if it's just 2 lines of code then it's cool.