docs(js): scope browser Special Use Cases to browser-only platforms

[mydea]

DESCRIBE YOUR PR

Stacked PR. Part of the JavaScript guide-categories series (#19492 → #19513). Depends on #19506; review/merge bottom-up.

The Special Use Cases overview and its browser-specific guides (Micro Frontends, Shared Environments / Browser Extensions, Offline Caching, Multiple Sentry Instances) are relevant only to browser SPAs. Replace their partial, stale backend notSupported lists with supportedCategories: [browser-only].

• Excludes meta-frameworks (astro, nextjs, nuxt, remix, …) and all server runtimes — the previous lists did this inconsistently (excluded the 13 original Node backends but still rendered on bun/cloudflare/deno/elysia/firebase/mastra).
• Offline Caching keeps its explicit notSupported (capacitor, cordova, electron, wasm).
• sentry-testkit intentionally left unrestricted (a transport-override testing tool usable in browser or Node tests).

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.
Select exactly one option. For deadlines, replace YYYY-MM-DD with the due date. You can update this information later by editing the PR description.

• Urgent deadline (GA date, etc.): YYYY-MM-DD
• Other deadline: YYYY-MM-DD
• No deadline: 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 supplied a deadline.

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

---

🤖 Generated with Claude Code

[vercel]

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

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Sep 23, 2026 7:59am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Sep 23, 2026 7:59am UTC

[chargome]

Is this one not also relevant for browser? e.g. oofline caching is also interesting for a nextjs app right?

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 21183ab. Configure here.}

[cursor]

Parent hide orphans child pages

Medium Severity

Scoping the Special Use Cases index to browser-only drops that sidebar folder on meta-frameworks and other non-browser-only platforms. Child pages that stay published—including Next.js deploying-on-cloudflare, plus unrestricted sentry-testkit and web-workers—lose their nav entry because a missing parent is omitted from the sidebar tree.

 

^{Reviewed by Cursor Bugbot for commit 21183ab. Configure here.}

[mydea]

Is this one not also relevant for browser? e.g. oofline caching is also interesting for a nextjs app right?

right, I will make offline caching browser instead of browser-only!

[sentry]

Bug: Inconsistent supportedCategories between the parent index page (browser) and child pages (browser-only) will cause some documentation pages to be hidden for meta-framework users.
_{Severity: LOW}

Suggested Fix

To ensure all child pages are visible for meta-framework guides, update the supportedCategories frontmatter in the affected child pages from [browser-only] to the broader [browser] category. This will align them with the parent index page and prevent them from being filtered out during the build process for platforms that don't define the browser-only category.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: docs/platforms/javascript/common/best-practices/index.mdx#L6-L7

Potential issue: There is an inconsistency in the `supportedCategories` frontmatter
property between a parent documentation page and its children. The parent index page for
'Special Use Cases' is assigned `supportedCategories: [browser]`, while several of its
child pages are assigned `supportedCategories: [browser-only]`. For meta-framework
platforms (e.g., Next.js) that do not include `browser-only` in their platform
categories, the build process will filter out these child pages. This results in a
degraded user experience where the index page is visible but appears incomplete, as it
will be missing links to the filtered-out child pages.

Also affects:

• docs/platforms/javascript/common/best-practices/micro-frontends.mdx:5~6
• docs/platforms/javascript/common/best-practices/shared-environments.mdx:5~6
• docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx:5~6

_{Did we get this right? 👍 / 👎 to inform future reviews.}

[coolguyzone]

LGTM, please resolve the issue brought up by the review bot.