Copy expo-random module to crypto

[aleqsio]

Why

Two modules have no clear separation of concerns and we want to do significant expansion on the crypto functionality to use the new TypedArrays expo-modules API.

It's easier if we sunset expo-random and use expo-crypto instead, as suggested by @tsapeta.

How

Copied functions, added a test screen to expo-crypto.

Test Plan

Copied existing tests, so the coverage should remain unchanged.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

[tsapeta]

Another thing to consider that we talked about: add warnings to functions in expo-random, so people upgrading to SDK 48 will see it.

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries

Your changes should be noted in the changelog. Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:

• packages/jest-expo/CHANGELOG.md

---

Generated by ExpoBot 🤖 against 929e2a3

[KiwiKilian]

Is there also a migration planned for expo-standard-web-crypto? It still uses expo-random.

Quick workaround otherwise is:

import * as Crypto from 'expo-crypto';

const webCrypto = typeof crypto !== 'undefined' ? crypto : Crypto;

if (typeof crypto === 'undefined') {
  Object.defineProperty(window, 'crypto', {
    configurable: true,
    enumerable: true,
    get: () => webCrypto,
  });
}

But actually I just noticed my usecase is solved with Crypto.randomUUID() – so I can drop uuid which needed the polyfill.

[tsapeta]

Yes, I think we'll eventually migrate expo-standard-web-crypto to use expo-crypto, but since this is just a JS package without native code, we can update it later, even after SDK release 🙂

That's perfect if Crypto.randomUUID() solves your issue though!