Skip to content

docs(react-router): add sentry init setup#18368

Draft
betegon wants to merge 8 commits into
masterfrom
docs/react-router-sentry-init
Draft

docs(react-router): add sentry init setup#18368
betegon wants to merge 8 commits into
masterfrom
docs/react-router-sentry-init

Conversation

@betegon

@betegon betegon commented Jun 11, 2026

Copy link
Copy Markdown
Member

DESCRIBE YOUR PR

Adds the experimental sentry init path to the React Router Framework Mode docs, following the TanStack Start setup pattern. The quick start now points users at npx sentry@latest init, explains how the AI-powered command works, and keeps manual setup as the detailed fallback.

The existing @sentry/wizard command remains available as the non-AI framework wizard path.

This follows the merged TanStack Start docs PR #17693 for the experimental sentry init flow, AI-powered command explanation, and manual-setup fallback pattern.

This also updates the manual setup callout and standardizes React Router Instrumentation API wording on 7.15+.

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

TEST PLAN

  • git diff --check
  • pnpm generate-doctree
  • Reviewed final diff to confirm verification/next-step content is restored from base
  • Not run: pnpm lint:typos (typos binary unavailable in this checkout)
  • Not run: pnpm build (local build requires NEXT_PUBLIC_SENTRY_DSN)

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
sentry-docs Error Error Jun 11, 2026 5:51pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview Jun 11, 2026 5:51pm

Request Review

If you're on a different version, you have two options:

1. **Recommended**: Use the <PlatformLink to="/features/instrumentation-api/">Instrumentation API</PlatformLink> (React Router 7.9.5+) for automatic tracing without Node version restrictions
1. **Recommended**: Use the stable <PlatformLink to="/features/instrumentation-api/">Instrumentation API</PlatformLink> (React Router 7.15+) for automatic tracing without Node version restrictions. React Router 7.9.5 introduced an earlier unstable API with `unstable_*` names.

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.

Leaving this note for reviewers: 7.15+ is intentional because the snippets here use the stabilized React Router instrumentation API (instrumentations). React Router 7.9.5 introduced the earlier unstable_* API, so the docs mention it but keep 7.15+ as the minimum for these examples.

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.

1 participant