Skip to content

feat(tanstackstart-react): Add component tracking#17875

Open
nicohrubec wants to merge 3 commits into
masterfrom
nh/tss-component-tracking
Open

feat(tanstackstart-react): Add component tracking#17875
nicohrubec wants to merge 3 commits into
masterfrom
nh/tss-component-tracking

Conversation

@nicohrubec
Copy link
Copy Markdown
Member

@nicohrubec nicohrubec commented May 26, 2026

Adds reactComponentAnnotation docs to the sentryTanstackStart Vite plugin page. Enabled in the SDK via getsentry/sentry-javascript#21149. This should be merged after the next SDK release (10.55.0).

Also changed the structure to have a separate section for each TSS specific option and put them all one level below the Configuration Options section.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 26, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment May 26, 2026 1:00pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview May 26, 2026 1:00pm

Request Review

@nicohrubec nicohrubec changed the title docs: Add component name annotation to TanStack Start feat(tanstackstart-react): Add component tracking May 26, 2026
@nicohrubec nicohrubec requested a review from s1gr1d May 26, 2026 12:38
@nicohrubec nicohrubec marked this pull request as ready for review May 26, 2026 12:38
## Tunnel Route
### Component Name Annotation

The `reactComponentAnnotation` option annotates your React components with `data-sentry-component` and `data-sentry-source-file` attributes at build time. This lets you see component names instead of generic selectors in Session Replay, breadcrumbs, and performance monitoring.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not 100% sure how we handle capitalization in the docs but we should be consistent here (as Replay is capitalized as it's a feature name but the others are not capitalized).

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From what I've seen this is the capitalization that we use in the docs everywhere so should be consistent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants