Repository navigation
Conversation
Contributor
size-limit report 📦
|
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
from
October 2, 2026 18:33
f3f2a5f to
6d76b74
Compare
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
2 times, most recently
from
October 3, 2026 16:14
28a0224 to
3a6835c
Compare
JPeer264
added this pull request to stack #25035
October 5, 2026 08:43
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
from
October 5, 2026 09:13
3a6835c to
08ff431
Compare
Member
Author
|
bugbot run |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 08ff431. Configure here.
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
from
October 5, 2026 11:15
08ff431 to
d5649bc
Compare
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
from
October 6, 2026 06:42
d5649bc to
85e1ba3
Compare
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
2 times, most recently
from
October 6, 2026 09:28
57d753d to
96ee28c
Compare
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
from
October 6, 2026 12:57
96ee28c to
9baf158
Compare
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
3 times, most recently
from
October 6, 2026 15:31
1c9f1fe to
87fce49
Compare
JPeer264
marked this pull request as ready for review
October 7, 2026 14:44
JPeer264
requested review from
andreiborza,
chargome,
logaretm and
mydea
and removed request for
a team,
andreiborza and
mydea
October 7, 2026 14:44
andreiborza
approved these changes
Oct 7, 2026
…udflare` `sentryCloudflareVitePlugin` wrapped the Worker entry of a vinext app with `withSentry` of `@sentry/cloudflare`, so the app sent Cloudflare data but no Next.js spans. In a build with the vinext plugins, the generated code now imports from `@sentry/nextjs/cloudflare` when it resolves from the entry. Other builds, and vinext builds without `@sentry/nextjs`, keep `@sentry/cloudflare`. Vite throws instead of returning `null` when `@sentry/nextjs` is installed in a version without the `./cloudflare` entry, so a throw of the resolve counts as unresolved. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/cloudflare-vite-vinext-nextjs-entry
branch
from
October 7, 2026 16:26
87fce49 to
a42fd95
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
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.

part of #19514
part of JS-1803
When a Vite build uses vinext and
@sentry/nextjs/cloudflareresolves from the Worker entry, the Vite plugin of@sentry/cloudflarenow wraps the entry withwithSentryfrom@sentry/nextjs/cloudflare. Other builds, and versions of@sentry/nextjswithout that entry, keep@sentry/cloudflare.Why
With
withSentryof@sentry/cloudflare, a vinext app on Workers sends Cloudflare data but no Next.js spans. Now it gets the Next.js spans without a config change.Traces
The same app and requests: vinext on Workers before and after this PR, and
next starton Node.js.GET /parameterized/42GET, 1 spanGET /parameterized/[id], 7 spansGET /parameterized/[id], 7 spansGET /api/helloGET, 1 spanGET /api/hello, 4 spansGET /api/hello, 4 spansGET /api/throw(error)GET, 1 spanGET /api/throw, 3 spansGET /api/throw, 3 spans