docs(javascript): drop non-canonical category values from frontmatter by mydea · Pull Request #19492 · getsentry/sentry-docs

mydea · 2026-09-18T10:23:19Z

DESCRIBE YOUR PR

Stacked PR. Bottom of the JavaScript guide-categories series (#19492 → #19506), based on master. Review/merge bottom-up.

Remove the javascript, server-node, and server-edge values from the categories frontmatter of all JavaScript platform pages and guides.

These values were declared only in frontmatter and never referenced by any filtering logic (PlatformCategorySection, SdkOption, platformLink, migrationGuide), nor were they part of the PlatformCategory type.
Removing them aligns the frontmatter data with the type. No functional change — every guide keeps its meaningful tags (browser, server, serverless, mobile, desktop).

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 · 2026-09-18T10:23:21Z

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

Project	Deployment	Actions	Updated
sentry-docs	Ready	Preview	Sep 21, 2026 8:13am UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Sep 21, 2026 8:13am UTC

Remove `javascript`, `server-node`, and `server-edge` from the `categories` frontmatter of all JavaScript platform pages and guides. These values were declared only in frontmatter and never referenced by any filtering logic (PlatformCategorySection, SdkOption, platformLink, migrationGuide) nor included in the `PlatformCategory` type. They carried no behavior. Removing them aligns the frontmatter data with the type, which already only permits `browser | desktop | mobile | server | serverless`. No functional change: every affected guide retains its meaningful tags (`browser`, `server`, `serverless`, `mobile`, `desktop`). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19492; review/merge bottom-up. Introduce two new `PlatformCategory` values, `browser-only` and `server-only`, and apply them across the JavaScript platform and guides. - `browser-only`: guides that run only in the browser (angular, react, vue, svelte, ember, gatsby, solid, wasm, capacitor, cordova) + the base Browser JavaScript platform. - `server-only`: guides that run only server-side (node, express, nestjs, and the serverless/edge runtimes). - Meta-frameworks that run in both (astro, nextjs, nuxt, remix, react-router, solidstart, sveltekit, tanstackstart-react) and electron get neither. - Also drops the redundant duplicate `categories` blocks from the effect and tanstackstart-react guide `config.yml` files (guide categories are read from `index.mdx`). ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19493; review/merge bottom-up. Node, Bun, and Deno are long-running server runtimes, not serverless/FaaS platforms, so the `serverless` category was semantically wrong for them. - The genuinely serverless guides (aws-lambda, azure-functions, gcp-functions, cloudflare, firebase) keep it. - No rendered content changes: `serverless` is always paired with `server` in every filter these guides retain, and the only `serverless`-alone consumers (migration items) are also gated by `frameworks:`. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19494; review/merge bottom-up. Extract the repeated `categories.includes('server') || includes('serverless')` logic into shared `hasServerCategory` / `hasBrowserCategory` helpers (`src/categories.ts`) and use them in `sdkOption` and `platformLink`. - Behavior-preserving cleanup; no rendered output changes. - The `nextjs`/`sveltekit` env-var exclusion in `shouldShowEnvVar` is intentionally left as a framework-specific special case. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com>

…ts (#19496) ## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19495; review/merge bottom-up. Key the “Only available on: Client/Server” hint in `getPlatformHints` off the new `isBrowserOnly` / `isServerOnly` category checks instead of hand-rolled runtime detection. - The hint is only informative on dual-runtime (meta-framework) platforms; on a single-runtime platform the option's runtime is already implied, so it's suppressed there. - Note: this also surfaces the hint on `desktop` (electron), which runs both a browser and a Node runtime. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19496; review/merge bottom-up. Add `supportedCategories` / `notSupportedCategories` frontmatter fields that gate common-content inheritance by platform category, alongside the existing guide-name `supported` / `notSupported` lists. - A page with `supportedCategories` is shown only for platforms/guides whose categories match; `notSupportedCategories` hides matching ones. - Lets pages target e.g. all server SDKs with `notSupportedCategories: [browser]` instead of enumerating every framework, and auto-covers new guides. - Both `isSupported` implementations (doc-tree collector and search collector) resolve categories and apply the new lists. Covered by `commonContentInheritance.spec.ts`. - This is the feature the remaining PRs in the stack build on. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19497; review/merge bottom-up. Replace the enumerated backend-framework `notSupported` lists on the Session Replay pages with `notSupportedCategories: [server-only]`, keeping non-category exclusions (`cordova`, `wasm`) explicit. - Session Replay is browser-only; the category form auto-covers every server-only SDK and picks up guides that were stale-omitted from the manual lists (effect, firebase, mastra). ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…19499) ## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19498; review/merge bottom-up. Convert the browser-only integration pages (breadcrumbs, browserapierrors, browserprofiling, replay, contextlines, globalhandlers, webworker, …) and best-practices/web-workers to `notSupportedCategories: [server-only]`. - Keeps non-category exclusions (cordova/wasm/electron/capacitor) explicit; auto-covers all server-only SDKs and picks up the stale-omitted backends. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…19500) ## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19499; review/merge bottom-up. Convert the feature-flag integration pages (launchdarkly, openfeature, statsig, unleash) to `notSupportedCategories: [server-only]`, keeping browser/desktop exclusions explicit. - These integrations ship in the browser bundle only. The change also makes the four pages consistent (statsig previously omitted hono/nitro). ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19501; review/merge bottom-up. Replace the enumerated server-framework `supported` lists on server-side integration pages (console, modules, onuncaughtexception, requestdata, trpc, unhandledrejection) with `supportedCategories: [server]`. - Keeps non-server platforms (electron) explicit; covers all server SDKs including meta-frameworks and picks up stale-omitted backends. - Only pages whose omissions were purely stale backends were converted; Node-only integrations are handled separately. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19502; review/merge bottom-up. The Supabase integration lives in `@sentry/core` and is re-exported by every SDK, so it is available on both browser and server platforms. - Set `supportedCategories: [browser, server]` (previously server only). - Drop the bogus `javascript.browser` key (not a real guide slug); the browser category now covers all browser SDKs. Keep `javascript.electron` explicit. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

#19504) ## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19503; review/merge bottom-up. IMPORTANT: This is for v11 and should only be merged when v11 is done. Rework the 26 Node auto-instrumentation integration pages to use `supportedCategories: [server]` with the specific edge runtimes the SDK does not support listed under `notSupported`, verified against the actual exports in `getsentry/sentry-javascript`. - Fixes stale hand-maintained lists: Node frameworks omitted from the old lists now show correctly, and Bun/Deno (which now export most Node integrations) are corrected per the SDK. - Exclude Cloudflare only (node+bun+deno): amqplib, dataloader, genericpool, graphql, kafka, knex, lrumemoizer, mongo, mongoose, mysql, mysql2, postgres, redis, tedious. - Exclude Deno+Cloudflare (node+bun): anr, http, fs, localvariables, nodecontext, pino. - Exclude Bun+Deno+Cloudflare (node-only/native): nodefetch, event-loop-block, nodeprofiling, noderuntimemetrics. - Exclude Deno (node+bun+cloudflare): prisma, prisma__v8.x. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…ages (#19505) ## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19504; review/merge bottom-up. Replace the enumerated server-framework `supported` lists on crons/*, mcp-monitoring, and the queues/caches instrumentation pages with `supportedCategories: [server]`. - These already listed all edge runtimes; the category form additionally covers guides stale-omitted from the manual lists. - MCP monitoring's `wrapMcpServerWithSentry` lives in `@sentry/core` and is runtime-agnostic, so `[server]` is accurate. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19506). Depends on #19505; review/merge bottom-up. Async context isolation applies to every server-side runtime, so replace the partial pure-Node backend `supported` list with `supportedCategories: [server]`. - Adds the page for the meta-frameworks, edge runtimes (bun/deno/cloudflare), and serverless targets that were previously missing. ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

…19511) ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

## DESCRIBE YOUR PR > **Stacked PR.** Part of the JavaScript guide-categories series (#19492 → #19513). Depends on #19511; review/merge bottom-up. Several Node/framework integrations were pinned to a handful of frameworks in hand-maintained lists even though the SDK exports them across server runtimes. Move them to `supportedCategories: [server]`, listing only the runtimes the SDK genuinely does not support under `notSupported`, verified against getsentry/sentry-javascript. - childProcess: node-only → exclude bun, deno, cloudflare (keep electron). - fastify: available across all server runtimes (node, bun, deno, cloudflare) — no exclusions. - koa / hapi: available across all server runtimes (node, bun, deno, cloudflare) — no exclusions. - postgresjs: available across all server runtimes (node, bun, deno, cloudflare) — no exclusions (the previous list wrongly listed only cloudflare/deno and omitted node/bun). - Removed the stale "only works in the Node.js and Bun runtimes" alerts from fastify, koa, and hapi. - connect and nest were left as-is — `connectIntegration` does not exist and `nestIntegration` is `@sentry/nestjs`-only (connect removal handled in the next PR). ## 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 - [x] 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](https://github.com/orgs/getsentry/teams/docs) --- 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

github-actions Bot added the Priority: Needs Triage The PR description is missing valid priority information label Sep 18, 2026

codeowner-assignment Bot requested a review from a team September 18, 2026 10:23

mydea added this pull request to stack #19507 September 18, 2026 10:24

github-actions Bot added Priority: Normal Docs review has no urgent deadline and removed Priority: Needs Triage The PR description is missing valid priority information labels Sep 18, 2026

vercel Bot deployed to Preview – sentry-docs September 18, 2026 10:31 View deployment

mydea marked this pull request as ready for review September 18, 2026 10:38

codeowner-assignment Bot requested a review from a team September 18, 2026 10:38

This was referenced Sep 18, 2026

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

Merged

docs(js): broaden server integration support via categories #19512

Merged

docs(js): remove Connect guide and integration (no longer supported) #19513

Closed

chargome approved these changes Sep 18, 2026

View reviewed changes

mydea force-pushed the guide-cat/01-drop-dead-categories branch from a13be7c to f801826 Compare September 21, 2026 08:06

vercel Bot deployed to Preview – sentry-docs September 21, 2026 08:13 View deployment

mydea merged commit 1289b1b into master Sep 21, 2026
22 checks passed

mydea deleted the guide-cat/01-drop-dead-categories branch September 21, 2026 08:30

Navigation Menu

Uh oh!

docs(javascript): drop non-canonical category values from frontmatter - #19492

docs(javascript): drop non-canonical category values from frontmatter#19492
mydea merged 1 commit into
masterfrom
guide-cat/01-drop-dead-categories

mydea commented Sep 18, 2026 •

edited

Loading

Uh oh!

vercel Bot commented Sep 18, 2026 •

edited

Loading

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

mydea commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

DESCRIBE YOUR PR

IS YOUR CHANGE URGENT?

SLA

PRE-MERGE CHECKLIST

Uh oh!

vercel Bot commented Sep 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

mydea commented Sep 18, 2026 •

edited

Loading

vercel Bot commented Sep 18, 2026 •

edited

Loading