Use @noble/hashes

[jacogr]

This requires BigInt ... so we are slightly held hostage by older versions of RN.

@Tbaut Do you know the state of BigInt support on RN? i.e. do these work in iOs/Android?

// test 1 (syntax)
const a = 1n + 2n;

// test 2 (does it have BigInt?)
const b = BigInt(1) + BigInt(2);

Trying to figure out what to do with this, i.e.

• specific (old-code) overrides for react-native (like we do elsewhere, RN has an own export & tested path)
• only allow react-native to use the WASM path (only caveat is crypto await before using)
• revisit every now and again until support appears and then go ahead here
• other?

I have been searching and it seem that iOs is probably less problematic than Android (which may be on a very old version of JSC). Then again, the info I could find has been very scarce.

[Tbaut]

Sorry about the late reply, I'm afk. Will try it out within the next week and let you know.

[jacogr]

The shims won’t do the trick at all. The issue is that it cannot polyfill stuff like 1n + 2n. In this case it is also a 3rd party that introduces it, so cannot use the Google polyfill.

But anyway, let‘s see. I think iOS has support, but android with JSC is always lagging.

So the current approach here is to detect if BigInt is available in the environment, i.e. typeof BigInt !== 'undefined' - if it is not available, it will just always use the WASM path.

[jacogr]

@Tbaut https://blog.logrocket.com/whats-new-in-react-native-0-65/ - it lists BigInt.prototype.toLocaleString under the Android updates.

[jacogr]

Following the approach with fallbacks when typeof BigInt === 'undefined'

[polkadot-js-bot]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.