Repository navigation
feat: opt-in error tracking - #20
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Category
Feature
Overview
Sends crash reports to our Bugsink at oops.peng.ly, but only when the build has
PUBLIC_SENTRY_DSNset. Deploy passes it in from the repo variable (already set), so forks and the Docker image build without it, and nothing Sentry ends up indist/at all.With it on, the layout gets one 283-byte script with two error listeners, and the Sentry SDK only downloads the first time something breaks. Sourcemaps upload during the deploy when the token and URL are set, and are deleted before anything's published.
Also groups
@sentry/*in Dependabot.Issue Number
N/A
Additional Info
Tested against a local Bugsink in a browser: nothing extra loads on a normal visit, and a thrown error pulled in the SDK and turned up as an issue. A build with upload on sent the maps and left none in
dist/.npm run validateandnpm testpass.