docs(nuxt): add sentry init setup

[betegon]

DESCRIBE YOUR PR

Adds the experimental sentry init path to the Nuxt 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 while preserving the Nuxt-specific dev and production verification notes.

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 wizard-generated example-page instructions are scoped to the existing wizard and next-step content is unchanged
• 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

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview, Comment	Jun 12, 2026 7:31pm
sentry-docs	Ready	Preview, Comment	Jun 12, 2026 7:31pm

[sergical]

lgtm but maybe we can introduce shared reusable components for the init command to make sure the content is the same across all the sdks / easiler to update / maintain

[sergical]

now that this is in a few places, i wonder if we can introduce a PlatformIncludes components these framework pages can share with a PlatformLink to make sure future components only require a component import vs text updates

[betegon]

doing it in a follow, great idea.

[betegon]

Good call. I opened a separate stacked follow-up for the shared include refactor here: #18400. Keeping this Nuxt PR scoped to the content change, and #18400 can be retargeted/rebased onto master after this lands.