You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d2c8ab0
Browse filesBrowse the repository at this point in the historyBrowse files
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
two SDK gaps on vinext: `openai` and `ioredis` get their diagnostics
channels from the build-time loader of webpack or Turbopack, which vinext
does not run. 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.
- `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>
"//": "Pin `ioredis` to 5.10.1: it's the last version before the driver publishes its own native diagnostics channels; orchestrion's config covers `ioredis <5.11.0`.",
0 commit comments