[experimental] Audit what we're about to release as web3.js Release Candidate for React Native

[steveluscher]

We have no React Native test harness, so we don't know if the new library actually works on React Native. Maybe it does, or maybe it's still missing some polyfills.

• Audit the library's compatibility with React Native (specifically RN >=0.7.0 with the Hermes engine)
• Wherever there are problems, either
  • Write our code differently to be naturally compatible, or
  • Create a fork of our code that is compatible (example: @solana/text-encoding-impl), or
  • Create a new package (eg. @solana/react-native-polyfill or something) that can be bare-imported to make things work

[steveluscher]

Are you still doing React Native stuff, @beeman?

[beeman]

Are you still doing React Native stuff, @beeman?

At the moment I'm not working on any React Native apps, but I'm happy to dive into it when I have some more free time, like right after HH Dubai.

[steveluscher]

I tried the new web3.js with a plain Expo app yesterday. With only the introduction of a SubtleCrypto polyfill (I used https://github.com/margelo/react-native-quick-crypto) I was able to generate keypairs and make RPC calls.

There's one ergonomic fix that needs to be made (#2898) and I think we can close this.