docs(js): use notSupportedCategories for feature-flag integrations

[mydea]

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
• 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 21, 2026 8:37am UTC

1 Skipped Deployment

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

[sentry]

Bug: The isSupported check relies on a server-only category in guide configs. Since server-only guides lack this category, integration pages will be incorrectly shown for them.
_{Severity: MEDIUM}

Suggested Fix

Ensure that the guide configurations for all server-side JavaScript platforms (e.g., aws-lambda, bun, node) include categories: ['server-only']. This could be done by merging the dependent PR that adds these categories first, or by including those configuration changes in this PR to make it self-contained.

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/launchdarkly.mdx#L4-L5

Potential issue: The code replaces an explicit `notSupported` platform list with
`notSupportedCategories: ['server-only']`. However, the `isSupported` function's check,
`matchesCategory(frontmatter.notSupportedCategories)`, will return `false` for
server-only guides like `aws-lambda`. This is because their guide configurations do not
define the `server-only` category, causing `guideFrontmatter.categories` to be an empty
array. As a result, integration pages intended for client-side platforms will be
incorrectly displayed on documentation pages for server-only platforms. This issue is
contingent on this PR being merged before the one that adds the necessary category
definitions to guide configs.

Also affects:

• docs/platforms/javascript/common/configuration/integrations/openfeature.mdx:4~5
• docs/platforms/javascript/common/configuration/integrations/statsig.mdx:4~5
• docs/platforms/javascript/common/configuration/integrations/unleash.mdx:4~5

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

[chargome]

unrelated but does this not work on electron? 🤔

[chargome]

quickly checked this should work on electron, we can fix this in a follow up