fix: fallback to "<environment unknown>" if navigator is undefined
#41
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
When using CloudFlare workers, the navigator is not available. The navigator is not even set to `undefined`, so we check for the exception instead, to make sure we always handle if it fails getting the user agent.
gr2m
reviewed
Feb 21, 2020
This was referenced Feb 21, 2020
Closed
Co-Authored-By: Gregor Martynus <gregor@martynus.net>
…s browser-specific the code will run in all kind of JS runtime environments
gr2m
changed the title
"<environment unknown>" if navigator is undefined
|
Thanks Oliver! |
|
🎉 This PR is included in version 4.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
When using CloudFlare workers, the navigator is not available.
The navigator is not even set to
undefined, so we check for the exception instead, to make sure we always handle if it fails getting the user agent.fixes: octokit/graphql.js#78