Skip to content

docs(javascript): add browser-only and server-only categories - #19493

Merged
mydea merged 2 commits into
guide-cat/01-drop-dead-categoriesfrom
guide-cat/02-add-browser-server-only
Sep 21, 2026
Merged

mydea merged 2 commits into
guide-cat/01-drop-dead-categoriesfrom
guide-cat/02-add-browser-server-only

Conversation

@mydea

@mydea mydea commented Sep 18, 2026 •

Copy link
Copy Markdown
Member

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
  • 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

vercel Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

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

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

Request Review

@codeowner-assignment
codeowner-assignment Bot requested a review from a team September 18, 2026 10:23
@github-actions github-actions Bot added the Priority: Needs Triage The PR description is missing valid priority information label Sep 18, 2026
@mydea
mydea added this pull request to stack #19507 September 18, 2026 10:24

@cursor cursor Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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

Fix All in Cursor

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

Reviewed by Cursor Bugbot for commit 1677007. Configure here.

Comment thread docs/platforms/javascript/guides/effect/index.mdx Outdated
@mydea
mydea marked this pull request as ready for review September 21, 2026 07:48
@codeowner-assignment
codeowner-assignment Bot requested a review from a team September 21, 2026 07:49
mydea and others added 2 commits September 21, 2026 09:51
Introduce two new `PlatformCategory` values, `browser-only` and
`server-only`, and apply them to the JavaScript platform and guides:

- `browser-only`: guides that run only in the browser (angular, react, vue,
  svelte, ember, gatsby, solid, wasm, capacitor, cordova) and the base
  Browser JavaScript platform.
- `server-only`: guides that run only server-side (node, express, fastify,
  nestjs, and the serverless/edge runtimes such as aws-lambda, cloudflare,
  bun, deno, etc.).
- Meta-frameworks that run in both (astro, nextjs, nuxt, remix, react-router,
  solidstart, sveltekit, tanstackstart-react) and electron (desktop) get
  neither tag.

These let content distinguish "runs only on the server" from "also runs on
the server" (which `server`/`serverless` alone cannot, since meta-frameworks
carry `server` too).

Also drop the redundant `categories` blocks from the effect and
tanstackstart-react guide `config.yml` files: guide categories are read from
`index.mdx` in the doc tree, so those duplicates were dead (and effect's had
drifted out of sync).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Effect is a general-purpose TypeScript library that runs in both the browser
and on a server, so it is a dual-runtime guide like the meta-frameworks: it
carries both `browser` and `server` and neither `browser-only` nor
`server-only`.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@mydea
mydea force-pushed the guide-cat/02-add-browser-server-only branch from ee5a132 to e5978f2 Compare September 21, 2026 08:06
@mydea
mydea merged commit ee4d740 into master Sep 21, 2026
24 checks passed
@mydea
mydea deleted the guide-cat/02-add-browser-server-only branch September 21, 2026 08:30
mydea added a commit that referenced this pull request Sep 21, 2026
## 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>

This branch was successfully deployed

2 active (1 outdated) deployments
Preview – sentry-docs — e5978f2f Deployed Sep 21, 2026 by vercel[bot]
Preview – develop-docs — 16770076 Deployed Sep 18, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Priority: Normal Docs review has no urgent deadline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants