Cloudflare released vinext, a ground-up reimplementation of the Next.js API as a Vite plugin targeting Cloudflare Workers. It replaces webpack with Vite and runs everything in the workerd runtime.
We're investigating what it would take to support it.
Initial assessment
- vinext supports
instrumentation.ts with the same register() + onRequestError() hooks our Next.js SDK uses
@sentry/cloudflare already has first-class Workers support@sentry/vite-plugin should handle source map upload- Our webpack/turbopack-based auto-instrumentation (wrapping loaders, route manifest, value injection) won't transfer — needs Vite equivalents
- Client-side routing instrumentation likely needs adaptation
- Server-side context propagation between vinext's separate RSC/SSR environments needs investigation
Status
Vinext is still experimental. We'll start with low-cost validation to see how far existing SDKs get us.
Please upvote this issue if you're looking for a solution here!
References
Cloudflare released vinext, a ground-up reimplementation of the Next.js API as a Vite plugin targeting Cloudflare Workers. It replaces webpack with Vite and runs everything in the workerd runtime.
We're investigating what it would take to support it.
Initial assessment
instrumentation.tswith the sameregister()+onRequestError()hooks our Next.js SDK uses@sentry/cloudflarealready has first-class Workers support@sentry/vite-pluginshould handle source map uploadStatus
Vinext is still experimental. We'll start with low-cost validation to see how far existing SDKs get us.
Please upvote this issue if you're looking for a solution here!
References