fix(randomUUID): add fallback when crypto.randomUUID is unavailable #510
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.
In some environments (non-secure origins like http, older browsers, certain test runners),
crypto.randomUUIDis not available, causing runtime errors.This change preserves the existing fast path when
crypto.randomUUIDexists, and adds a RFC4122 v4-shaped fallback for other cases:crypto.randomUUID.bind(crypto)when presentNo breaking changes.