Skip to content

docs(js): Move the Cloudflare quick starts into the framework guides - #19977

Merged
JPeer264 merged 10 commits into
masterfrom
jp/poc-c-runtime-quick-starts
Nov 10, 2026
Merged

JPeer264 merged 10 commits into
masterfrom
jp/poc-c-runtime-quick-starts

Conversation

@JPeer264

@JPeer264 JPeer264 commented Oct 14, 2026 •

Copy link
Copy Markdown
Member

DESCRIBE YOUR PR

This moves the pages under Cloudflare → Frameworks into their framework guides as "Quick Start (Cloudflare)", right below the default quick start, for example /guides/nextjs/cloudflare/. This applies to Astro, Hono, Next.js, Nuxt, Remix, SvelteKit and TanStack Start. The pages keep their content, and the old URLs redirect.

  • Next.js on Cloudflare is now a full quick start (wizard, Wrangler configuration, withSentry Worker entry for OpenNext and vinext, verification).
  • The Hydrogen guides move into the React Router guide (Hydrogen 2025.5.0 and later) and the Remix guide (older versions, as "Hydrogen (Legacy)").
  • Cloudflare → Frameworks redirects to the Cloudflare quick start, which links to every framework page.
  • The TanStack Start page now installs @sentry/tanstackstart-react, which its code imports, and its Wrangler and source maps sections render again.

Each framework with quick starts for more than one runtime also gets a runtime selector. It is static HTML, so the Markdown export for agents has the same links as a "Runtime" list:

Image

Hono decision

The Hono page moves as it is: it shows the Cloudflare install and configure steps, and links to the Hono quick start for the rest. The Hono quick start already covers Cloudflare in its runtime tabs, so the alternative is to redirect the old page there. A full Cloudflare quick start and the runtime selector for Hono will come in a follow up, because the Hono guide needs some rework.

Known issues

  • No Bun or Deno quick starts for Next.js and Nuxt, because the SDK repo has no tests for them on these runtimes.
  • The Next.js verify step builds with opennextjs-cloudflare, so it does not apply to vinext apps.

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

@vercel

vercel Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
develop-docs Ready Ready Preview Nov 10, 2026 12:59pm UTC
sentry-docs Ready Ready Preview Nov 10, 2026 12:59pm UTC

Request Review

@github-actions github-actions Bot added the Priority: Normal Docs review has no urgent deadline label Oct 14, 2026
@JPeer264
JPeer264 force-pushed the jp/poc-c-runtime-quick-starts branch from 6aba671 to 25eb763 Compare October 21, 2026 09:09
@JPeer264 JPeer264 changed the title docs(js): [Experiment] Cloudflare quick starts in the Next.js and Nuxt guides docs(js): Add Cloudflare quick starts to the Next.js and Nuxt guides Oct 21, 2026
@JPeer264
JPeer264 added this pull request to stack #20127 October 21, 2026 11:38
@JPeer264
JPeer264 force-pushed the jp/poc-c-runtime-quick-starts branch from 25eb763 to 3bdd530 Compare October 21, 2026 12:13
@JPeer264
JPeer264 force-pushed the jp/poc-c-runtime-quick-starts branch from 3bdd530 to 1385cf6 Compare October 25, 2026 22:25
@JPeer264
JPeer264 force-pushed the jp/poc-c-runtime-quick-starts branch from 1385cf6 to 04d1d99 Compare October 30, 2026 17:59
@JPeer264
JPeer264 removed this pull request from stack #20127 October 31, 2026 18:16
@JPeer264 JPeer264 changed the title docs(js): Add Cloudflare quick starts to the Next.js and Nuxt guides docs(js): Move the Cloudflare quick starts into the framework guides Oct 31, 2026
@JPeer264
JPeer264 force-pushed the jp/poc-c-runtime-quick-starts branch from 6b3fb32 to b91b19e Compare October 31, 2026 18:46
@JPeer264
JPeer264 added this pull request to stack #20366 October 31, 2026 18:47
@JPeer264
JPeer264 added this pull request to stack #20468 November 4, 2026 16:05
@JPeer264
JPeer264 marked this pull request as ready for review November 4, 2026 17:19
@JPeer264 JPeer264 self-assigned this Nov 4, 2026
@JPeer264
JPeer264 requested a review from chargome November 4, 2026 17:20
@cursor

cursor Bot commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Getting ready to monitor this change · Rollout details

Status Service Environment
⏳ Getting ready to monitor this change

JPeer264 and others added 9 commits November 10, 2026 10:08
The Next.js and Nuxt guides get a "Quick Start - Cloudflare" page below the
default quick start. Both quick starts move into getting-started-node and
getting-started-cloudflare includes per framework, so they share their
content. The Next.js on Cloudflare quick start now also covers wrapping
the Worker entry with withSentry.

The Next.js and Nuxt pages under Cloudflare > Frameworks and the Next.js
"Deploying on Cloudflare Workers" page redirect to the new pages.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The label reads as a variant of the Quick Start above it, without a
spaced hyphen that looks like a dash.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…rk guides

The Astro, Remix, SvelteKit and TanStack Start pages under Cloudflare >
Frameworks move into their framework guides as "Quick Start - Cloudflare",
like Next.js and Nuxt. The Cloudflare parts of the Astro, Remix and
SvelteKit includes move into getting-started-cloudflare includes, because
PlatformSection only shows them on pages in the Cloudflare guide. The
framework list on the Cloudflare quick start links to the new pages, and
the old URLs redirect.

The TanStack Start page now installs @sentry/tanstackstart-react, which
its code imports, and its Wrangler and source maps sections render again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Hono page under Cloudflare > Frameworks moves into the Hono guide as
"Quick Start - Cloudflare". The Remix "Cloudflare SDK Guide" page only
linked to the Remix Cloudflare quick start and to Hydrogen, so it
redirects to the Remix Cloudflare quick start, which now links to the
Hydrogen guides.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ides

The Hydrogen with React Router guide moves into the React Router guide as
"Quick Start - Hydrogen", and the legacy Hydrogen with Remix guide moves
into the Remix guide. They were the last pages under Cloudflare >
Frameworks. The framework list on the Cloudflare quick start links to the
new page, and the old URLs redirect.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
All framework pages moved into their framework guides, so the Cloudflare
> Frameworks page only listed links. The Cloudflare quick start already
links to every framework page, so the old URL now redirects there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use the same label as the Next.js and Nuxt Cloudflare quick starts.
The Hydrogen quick start in the React Router guide becomes
"Quick Start (Hydrogen)".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each framework guide now has a Node.js and a Cloudflare quick start, so
quick starts set `runtime` in their frontmatter. On each page with
`runtime`, DocPage renders a runtime selector at the top of the content.
It links the guide page and its child pages that set `runtime`. The links
are plain anchors, so they are also in the Markdown export, which marks
the current page with "(current page)".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Moving the Nuxt quick start into an include turned two PlatformLinks into
fixed links. The include only renders in the Nuxt guide, so the
PlatformLinks resolve to the same pages.

Co-Authored-By: Jan Peer Stöcklmair <jan.peer@sentry.io>
If a guide has quick starts for more than one runtime, the sidebar link to the guide page
is "Quick Start (Node.js)" and not "Quick Start". It then matches the links to the other
quick starts, for example "Quick Start (Cloudflare)". The runtime comes from the same
links as the runtime selector.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@JPeer264
JPeer264 merged commit 1a2e1ef into master Nov 10, 2026
30 checks passed
@JPeer264
JPeer264 deleted the jp/poc-c-runtime-quick-starts branch November 10, 2026 16:15
JPeer264 added a commit that referenced this pull request Nov 10, 2026
## DESCRIBE YOUR PR

This links the runtime quick starts of the agent guides, so a reader or
a coding agent can start on one page and find the setup for their
runtime. Pi Durable, Mastra and Flue set `runtime` in their frontmatter,
so they show the runtime selector from #19977, and Pi Durable gets new
Deno and Bun quick starts.

- The framework dropdown on the Node.js, Bun, Deno and Cloudflare quick
starts gets an "Agent frameworks" group (Eve, Flue, Mastra and Pi
Durable). Each entry opens the quick start for that runtime.
- On Deno, the app loads the Sentry import hook with `--preload`, and
`deno.json` needs `nodeModulesDir`. On Bun, the app must be built with
`sentryBunPlugin`, because Bun has no runtime hook.

## Dropdown decision

"Agent frameworks" comes before "Set up with its own guide", so the
agent guides are near the top of the dropdown. The alternative is to
show them last.

## Known issues

- The SDK repo has no tests for Pi Durable on Deno or Bun yet. Both
setups were tested locally with a fake model provider.

## 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)

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

This branch was successfully deployed

2 active deployments
Preview – sentry-docs — c79a5bc1 Deployed Nov 10, 2026 by vercel[bot]
Preview – develop-docs — c79a5bc1 Deployed Nov 10, 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