Repository navigation
Only load Sentry on the production site - #282
Merged
Merged
Conversation
Deploying slaytheweb with
|
| Latest commit: |
0394db6
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6c5862c0.slaytheweb.pages.dev |
| Branch Preview URL: | https://sentry-prod-only.slaytheweb.pages.dev |
This file contains hidden or 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
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.
Sentry was loaded on every host except localhost, so forks, previews and copies hosted elsewhere (e.g. run.app, see SLAYTHEWEB-M1) were sending errors to our project.
Now the Sentry loader only runs on slaytheweb.cards and www.slaytheweb.cards. As a second layer,
allowUrlslimits reported errors to scripts served from those origins. Nothing else in the codebase calls Sentry, so there is nothing to break when it isn't loaded.