Repository navigation
Conversation
Contributor
size-limit report 📦
|
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 2, 2026 18:33
d2c8ab0 to
cd09798
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
2 times, most recently
from
October 3, 2026 16:14
e4ac7e8 to
a2528b7
Compare
JPeer264
added this pull request to stack #25035
October 5, 2026 08:43
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 5, 2026 09:13
a2528b7 to
9af8da5
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 5, 2026 11:15
9af8da5 to
4d33f68
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
2 times, most recently
from
October 6, 2026 07:27
84f9919 to
fd788b5
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 6, 2026 09:28
fd788b5 to
943dd4a
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 6, 2026 12:57
943dd4a to
c2e7c67
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
3 times, most recently
from
October 6, 2026 15:31
cdd5443 to
3419f77
Compare
JPeer264
marked this pull request as ready for review
October 7, 2026 14:49
JPeer264
marked this pull request as draft
October 7, 2026 14:50
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 7, 2026 16:00
3419f77 to
785f56b
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 7, 2026 16:04
785f56b to
c12fa59
Compare
JPeer264
marked this pull request as ready for review
October 7, 2026 16:04
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
2 times, most recently
from
October 8, 2026 08:01
7971d8a to
b36a03f
Compare
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 8, 2026 08:46
b36a03f to
09df1d7
Compare
Base automatically changed from
jp/cloudflare-vite-vinext-nextjs-entry
to
develop
October 8, 2026 11:28
JPeer264
requested review from
andreiborza and
mydea
and removed request for
a team
October 8, 2026 11:28
vinext builds a Next.js app with Vite. Its e2e tests run in two places: - nextjs-16 gets the optional variants `nextjs-16 (vinext)` and `nextjs-16 (vinext, bun)`. vinext builds the same app, and the same tests run as for Next.js. They skip the checks of the Next.js build output, and what vinext can not do yet: `openai` and `ioredis` get their diagnostics channels from the build-time loader of webpack or Turbopack, which vinext does not run, and without a Sentry build plugin there is no component annotation and no module metadata for the third-party filter. The OpenNext wrangler config is now `wrangler.opennext.jsonc`, because vinext refuses to build without the Cloudflare plugin when the project root has a wrangler config. The vinext build keeps `@opennextjs/cloudflare` external, because the D1 route of the OpenNext variants imports it, and its `import()` of a computed specifier can not be bundled. - `vinext-cf-workers` covers vinext on Workers. Its Worker entry has no Sentry calls, so `sentryCloudflareVitePlugin` must wrap it with `withSentry` from `@sentry/nextjs/cloudflare`. The app also has the server config of a Next.js app, whose `init` must create no second client in the Worker. The tests check that each request has one `http.server` span with the route of Next.js and the Next.js spans in its segment, that an incoming trace is continued in that segment, and that an error from `onRequestError` is in the trace of the request. There is no Deno variant. On Deno, the `node:http` server of vinext starts each request after the first one in the AsyncLocalStorage store of an earlier request, also without Sentry, so vinext creates no request span. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
JPeer264
force-pushed
the
jp/vinext-e2e-tests
branch
from
October 8, 2026 11:28
8ead2fc to
9ef6e7e
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.
part of #19514
part of JS-1803
This adds e2e tests for vinext.
nextjs-16gets the optional variantsnextjs-16 (vinext)andnextjs-16 (vinext, bun), which build the same app with vinext and run the same suite. The new appvinext-cf-workerscovers vinext on Workers through the Vite plugin of@sentry/cloudflare.Known issues
openaiandioredisspans: vinext does not run the build-time loader of webpack or Turbopack.fetchspans on Bun: vinext keeps thefetchfrom beforeSentry.init.node:httpserver of vinext leaks the AsyncLocalStorage store between requests, also without Sentry.