[@expo/cli] Avoid dependency on uuid #20479
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
Older versions of uuid is deprecated. This will start using a secure random source, and will produce one less deprecation warning when installing!
How
The
@expo/cli
package only used the UUID v4 function from a Node.js context, and Node.js already have arandomUUID
function built in.Test Plan
I'm not sure, since this is used in the tests I'm hoping the CI will cover it? 馃槄
Checklist
expo prebuild
& EAS Build (eg: updated a module plugin).