Conversation
Contributor
size-limit report 📦
|
JPeer264
force-pushed
the
jp/nextjs-cloudflare-entry
branch
2 times, most recently
from
October 2, 2026 19:29
fb54ebb to
fda7a91
Compare
`withSentry` from `@sentry/nextjs/cloudflare` wraps the Worker entry of a Next.js app on Cloudflare Workers, e.g. `.open-next/worker.js` of OpenNext or the fetch handler of vinext. It is `withSentry` of `@sentry/cloudflare` with the Next.js handling added: - It installs the OpenTelemetry async context strategy and context manager at module load, so the spans of Next.js nest and keep their OpenTelemetry context as on Node.js. - Its client gets the span hooks and `ignoreSpans` of the server `init`, the event processor for the control flow errors of React, the `use cache` integration, the Sentry propagator and the Next.js SDK metadata. - The propagator keeps the request span as parent when Next.js extracts an incoming trace that the root span already continued. Next.js does this when it misses its router server context, e.g. on Workers where `process.cwd()` is `/bundle`, and each continued request then had two segments. - The request spans of Next.js (`BaseServer.handleRequest`) are ignored, so the request span of `withSentry` is the only `http.server` span. The other Next.js spans become its children; it gets the route from their `next.route` and its status from the response. When the middleware answers the request or throws, the span is named `middleware GET`, like the middleware segment on Node.js. - Requests to the tunnel route are not sampled. - The server and edge `init` in `sentry.*.config.ts` create no client in the Worker. They hand over the build release of `withSentryConfig`, which only code that Next.js compiles can read. The `nextjs-16-cf-workers` e2e app now uses it. This runs the server tests that were skipped, and adds tests for D1 spans, the OpenTelemetry context and trace continuation. Its `compatibility_date` moves to 2026-02-19, the first date on which Next.js extracts the incoming trace again. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/nextjs-move-server-span-hooks
branch
from
October 3, 2026 16:14
051bd51 to
81f62d0
Compare
JPeer264
force-pushed
the
jp/nextjs-cloudflare-entry
branch
from
October 3, 2026 16:14
fda7a91 to
1f9ac0a
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
withSentryfrom@sentry/nextjs/cloudflarefor the Worker entry of a Next.js app on Cloudflare Workers, for example.open-next/worker.jsof OpenNext or the fetch handler of vinext. It iswithSentryof@sentry/cloudflarewith the Next.js handling of the serverinitadded, so a Next.js app on Workers gets the spans it gets on Node.js from one wrapper, without new options. This is the only new public API.Decisions:
@sentry/cloudflareloses the OpenTelemetry context of the Next.js spans, so their parents and context values break.BaseServer.handleRequest) are ignored, so the request span ofwithSentryis the onlyhttp.serverspan. The other Next.js spans become its children; it gets the route from theirnext.routeand its status from the response. When the middleware answers the request or throws, the span is namedmiddleware GET, like the middleware segment on Node.js.compatibility_date2026-02-19,process.cwd()is/bundleduring a request. Next.js then misses its router server context and extracts the incoming trace again. The propagator keeps the request span as parent in that case, else each continued request has two segments.sentry.server.config.tsandsentry.edge.config.tsstill run in the Worker but create no client there. They hand over the build release ofwithSentryConfig, which only code that Next.js compiles can read. Their other options do not apply, and a debug log says so.instrumentation.tsdrops them too.@sentry/cloudflarebecomes a dependency of@sentry/nextjs. Its dependencies are already in the dependency tree of@sentry/nextjs.Known difference: on Workers, a release from the
withSentryoptions,SENTRY_RELEASEorCF_VERSION_METADATAwins over the build release. On Node.js, the build release wins over the environment.The
nextjs-16-cf-workerse2e app now uses it, which un-skips its server tests and adds tests for D1 spans, the OpenTelemetry context and trace continuation.🤖 Generated with Claude Code