feat: add React + Sentry example#1
Open
Catalin4513 wants to merge 7 commits into
Open
Conversation
# Conflicts: # README.md
…rror demo to a multi-record sync
Author
|
@vmihailenco, PTAL |
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.
Adds the first example to the repo: a minimal React (Vite + TypeScript) todo app instrumented with
@sentry/react, sending data to Uptrace via Uptrace's Sentry-compatible ingest endpoint.What it shows
Error,TypeError,RangeError,TodoSyncError), raised a few frames deep so the stack trace has real app frames.Sentry.captureMessage()at a random level (info / warning / error).run_traced_taskwith two child spans; browser tracing also emits page-load/navigation spans.Wiring
The only Uptrace-specific code is a plain
Sentry.init({ dsn })insrc/instrument.ts; the DSN comes fromVITE_SENTRY_DSN. The README walks through copying the Sentry DSN from a project's Data Source Name page, configuring.env, running withnpm run dev, and where each signal appears in the Uptrace UI.Verified:
tsc -b+vite buildpass; empty and populated states render correctly in a headless Chrome check.