SDK: Fallback to url-parse if URL is not available
#800
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In some environments (e.g. Cloudflare Workers), the `URL` component cannot be resolved altogether. It is neither available as nodejs `url` module nor as browser's `window.URL` object. To handle this extreme case, we are adding a last resort fallback to `url-parse`.
tomaszslabon
approved these changes
Mar 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 (e.g. Cloudflare Workers), the
URLcomponent cannot be resolved altogether. It is neither available as nodejsurlmodule nor as browser'swindow.URLobject. To handle this extreme case, we are adding a last resort fallback tourl-parse.