ci: test on macOS

[legobeat]

• github ci: test on macOS-latest

---

Related

• Based on test node.js v16 runtime compatibility #153
• meta: Indicate compatible Node.js versions #152 (comment)

[paulmillr]

I think cross platform testing makes sense for some cases:

1. when pkg is using underlying os api which is different accross oses (fs etc)
2. When it’s infrastructural pkg which is getting built accross oses (ethereum-cryptography)

I don’t want to test parcel, browserify etc compat inside of noble curves but it makes sense to keep doing it in eth cryptography.

so, why do you think we should test builds on macos? This would just increase build times unnecessarily.

Something like testing in different runtime (bun) would make more sense.

[legobeat]

so, why do you think we should test builds on macos?

It was motivated by this comment:

I don’t know how to test v14, because nodejs 14 on arm macs is unavailable.

It simply seemed desired!

[paulmillr]

ah, that was meant for eth-cryptography.

do you know what we need to make curves v14-compatible?

[legobeat]

ah, that was meant for eth-cryptography.

Maybe worth the tradeoff there, then, at least? :)

• github ci: test on macOS ethereum/js-ethereum-cryptography#123

do you know what we need to make curves v14-compatible?

Unless I'm missing something, I think getting a new release of @noble/hashes (I went on a limb and made an RC) into @noble/curves might be enough to do it. Happy to take a look!

[legobeat]

Happy to take a look!

Update: It seems like this is also necessary to make the crypto module available in Node.js v14: paulmillr/noble-hashes#98

I do find it curious that this is not caught during unit tests of @noble/hashes but it did come up when trying to use the lib in @noble/curves on Node.js v14.