Repository navigation
Add support for Cloudflare WorkerEntrypoint #15942
Description
Hi all, it's great to see Cloudflare Workers getting some attention. Cloudflare seem to be moving towards the WorkerEntrypoint/class-based approach. E.g., RPC methods (worker-to-worker requests) are only supported with WorkerEntrypoint: https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/rpc/#the-workerentrypoint-class
Are there plans to support this structure?
*Originally posted by @CameronB15 in *#12620
Metadata
Metadata
Assignees
Projects
- Status
Activity
hcharlie1201 commentedon Sep 20, 2025
Whats the alternative to monitor errors lol...
Mael-Abgrall commentedon Sep 20, 2025
@hcharlie1201 you should subscribe to:
andreiborza commentedon Sep 22, 2025
Hi @hcharlie1201, the cloudflare sdk will receive more attention soon. It's on our plate, but we don't have an ETA yet, sorry.
FraBle commentedon Feb 26, 2026
@JPeer264 I saw you self-assigning. Does this mean it's actively been worked on?
Edit: I'm very selfishly hoping that #14387 might get tackled as part of that.
JPeer264 commentedon Feb 26, 2026
Yes this is on the roadmap for the next week(s) to be added. It is one of the highest voted issues so this has community priority.
@FraBle I assume you mean #14387, right? If so, I'll can take a look at that as well ;)
alexandersmpx commentedon Mar 2, 2026
Yes please!
feat(cloudflare): Support basic WorkerEntrypoint (#19884)
JPeer264 commentedon Apr 7, 2026
FYI I just merged #19884 which adds basic support for the
WorkerEntrypointon the next release. This can then be used like normal exported handlers:Sentry.withSentry(() => ({}), MyWorkerEntrypoint). Right now RPC calls are not instrumented, which makes the instrumentation a little less useful for now. This will be then added with #16898. Until this is fully supported I'll leave this issue open.feat(cloudflare): Support rpc trace propagation for WorkerEntrypoint (#…
github-actions commentedon May 7, 2026
A PR closing this issue has just been released 🚀
This issue was referenced by PR #20523, which was included in the 10.52.0 release.