docs(js): broaden server integration support via categories

[mydea]

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
• 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 22, 2026 1:31pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
develop-docs	Ignored	Preview	Sep 22, 2026 1:31pm UTC

[sentry]

Bug: The documentation for the postgresjs integration is incorrectly shown for Node.js and Bun runtimes, where the integration is not actually supported.
_{Severity: LOW}

Suggested Fix

Update the supportedCategories in postgresjs.mdx to accurately list only the supported runtimes, such as ['deno', 'cloudflare'], instead of the general [server] category. This will ensure the documentation is only visible for platforms where the integration is available.

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/configuration/integrations/postgresjs.mdx#L1-L8

Potential issue: The change to `supportedCategories: [server]` in the `postgresjs.mdx`
file incorrectly makes the documentation for the `postgresjs` integration visible for
all server runtimes, including Node.js and Bun. However, the `instrumentPostgresJsSql`
integration is not supported on these platforms; it is only available for Deno and
Cloudflare. This inconsistency will mislead users on Node.js and Bun into thinking the
feature is available to them, causing confusion and potential implementation errors when
they find it doesn't work.

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