feat: add client-side sentry tracking#54
Open
h1065153539-create wants to merge 1 commit into
Open
Conversation
|
@h1065153539-create is attempting to deploy a commit to the Meshack Yaro 's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
Description
Adds client-only Sentry error tracking for the Pages Router app shell. The browser client initializes only when
NEXT_PUBLIC_SENTRY_DSNis configured, so local development and CI builds do not send events by default.Related Issue
Closes #6
Type of Change
Changes Made
@sentry/nextjsand lockfile updates.NEXT_PUBLIC_SENTRY_DSN..env.exampleand README.Screenshots (if applicable)
No visual UI change intended. The only rendered fallback is the error boundary screen shown after an unexpected client-side render error.
Checklist
npm run lintand fixed all issuesnpm run typecheckwith no errorsnpm run buildsuccessfullyAdditional Notes
Verification run locally:
npm run lintnpm run typechecknpm run buildnext start -p 3016served/with HTTP 200 and titleTrustFlow - Decentralized Escrow on Stellar.This PR intentionally does not add server or edge Sentry instrumentation, source-map upload configuration, or project auth secrets because the issue asks for React client tracking only.