docs(cloudflare): Add new /nodejs_compat entrypoint

[JPeer264]

DESCRIBE YOUR PR

This adds a new page for the /nodejs_compat entrypoint. There is also a tiny note in the quickstart that this can be unlocked, making sure that people know by just reading the quickstart

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

• Urgent deadline (GA date, etc.):
• Other deadline:
• None: 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 added an urgent due date to it.
  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

LEGAL BOILERPLATE

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

EXTRA RESOURCES

• Sentry Docs contributor guide

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
sentry-docs	Ready	Preview	Jul 14, 2026 11:45am

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ignored	Preview	Jul 14, 2026 11:45am

[github-actions]

⚠️ Redirect Chain Issues Detected

This PR introduces or contains redirect chains that degrade SEO and add latency.

Content Links Pointing to Redirects (2 found)

These links point to URLs that redirect. Update them to point directly to the final destination:

File	Line	Current Link	Should Be
platform-includes/llm-rules-logs/javascript.nextjs.mdx	3	/ai/agent-skills/	/ai/agent-plugin/
platform-includes/llm-rules-logs/javascript.nextjs.mdx	15	/ai/agent-skills/	/ai/agent-plugin/

---

Each redirect hop loses ~15% of SEO link equity and adds latency for users.

[sentry]

Bug: The relative link ../../features/nodejs-compat in javascript.cloudflare.mdx will likely break because the file is included in a different context, causing the path to resolve incorrectly.
_{Severity: LOW}

Suggested Fix

Replace the relative markdown link ../../features/nodejs-compat with a platform-aware component like <PlatformLink> or an absolute path. This ensures the link resolves correctly regardless of the context in which the content is included, following the established pattern in the documentation codebase.

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: platform-includes/configuration/integrations/javascript.cloudflare.mdx#L18-L19

Potential issue: The file
`platform-includes/configuration/integrations/javascript.cloudflare.mdx` is a
platform-specific content file that is included in other documentation pages. It
contains a relative markdown link `../../features/nodejs-compat`. When this content is
rendered on a different page, the relative path will be resolved from the new page's
location, not the original file's location. This will cause the link to point to an
incorrect or non-existent URL, resulting in a broken link for the user.

[coolguyzone]

Looks good!