Repository navigation
Investigate cloudflare support #18669
Description
Activity
- added a parent issue
on Jan 2, 2026 Some thoughts from my side.
- Entrypoint: Cloudflare needs to have a wrapper around functions which are exported of the
start.ts, there is no way around it - Entrypoint: We could theoretically add our own "entrypoint" like following and steer everything via environment variables:
That means that our entrypoint would just import
// wrangler.jsonc { "main": "@sentry/tanstackstart-react/cloudflare/server-entry" }
@tanstack/react-start/server-entry, wrap everything and export it - Cloudflare can't have integrations with OpenTelemetry monkey patching, so we need to define which integrations are possible (this could even be a general Cloudflare SDK topic)
- I'm currently not sure if it is possible to use Cloudflare specific handlers, such as queue (if so we need to see if we wrap the entrypoint with
@sentry/tanstackstart-reactor@sentry/cloudflare. nodejs_compatis required in the compatibility settings- I wouldn't add support for legacy Cloudflare Pages with
pages_build_output_dirin thewrangler.jsonc, as everything goes to Cloudflare Workers with its "assets"
- Entrypoint: Cloudflare needs to have a wrapper around functions which are exported of the
- added a commit that references this issue
on Mar 30, 2026 Hey guys, I'd love for this to be supported. I'm running a TanStack Start (React) on Cloudflare. I have a custom entrypoint with
) is paramount. Let me know if I can provide any additional info. Thanks!fetch,queueandscheduled. Myfetchhas a bunch of logic and then ends up calling@tanstack/react-start/server-entry. I'd argue unobfuscating server functions (like you guys already do here:How exactly are you running your custom fetch logic in Cloudflare? I'd like to know if there are different techniques for it. Have you already tried to get Sentry up and running with your setup?
- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Apr 27, 2026 How exactly are you running your custom fetch logic in Cloudflare? I'd like to know if there are different techniques for it.
Thanks for the extremely quick reply @JPeer264. I'm using both Cloudflare Sandbox and Dynamic Workers to handle some requests that are not supposed to be passed to Tanstack Start. My endpoint roughly looks like this:
import handler from "@tanstack/react-start/server-entry"; export default { async fetch(request: Request, env: Cloudflare.Env, ctx: ExecutionContext) { if (requestToSandbox(request) { return proxyToSandbox(request); } if (requestToDynamicWorker(request)) { return dynamicWorkerHandler(request); } if (request.method === "GET" || request.method === "HEAD") { const asset = await env.ASSETS.fetch(request); if (asset.status !== 404) return asset; } return handler.fetch(request); }, async queue(batch: MessageBatch<{ type: string }>) { // Handle jobs }, async scheduled() { // Handle crons }, }
Ideally, I be able to capture errors from
handler.fetch(request),queueandscheduledand ignore everything else but I'll take whatever's feasible.Have you already tried to get Sentry up and running with your setup?
I didn't because I saw this "This setup does not currently work for Cloudflare deployments." on the setup docs: https://docs.sentry.io/platforms/javascript/guides/tanstackstart-react/#without---import-flag-eg-vercel-netlify. But I can give it a go.
Ok that makes sense, thx for the setup. Could you try to follow the Cloudflare SDK setup? It looks like it could work in that case. The only issue is that Tanstack specific traces wouldn't be there.
- moved this from Waiting for: Product Owner to No status in GitHub Issues with 👀 3
on Apr 27, 2026 - removed a parent issue
on Apr 29, 2026 - added a parent issue
on Apr 29, 2026 - added a commit that references this issue
on May 13, 2026
At the moment we document and test only nitro. We should investigate whether our SDK works properly with Cloudflare and document what needs to be done to set this up. Ideally we add an E2E app to test this.