Was excited to start using trigger.dev on Cloudflare Worker, as trigger.dev seems to be the most developed workflow tool to use in your own code. pulled up the hono example, and it's for version 2. I don't see any guides on trigger.dev anymore for Cloudflare Workers environment for version 3. Just Bun, Nodejs. So did you drop support for Cloudflare Workers in v3? If so, huge mistake. If not, any guides for this or will this not work on Cloudflware Workers?
#Does this no longer work on Cloudflare Workers?
maiden schooner
shadow grail
Code isn’t executed on your existing server with v3, for many reasons that resulted in low reliability and bad DX.
You can still use your existing CF apps with Trigger: triggering runs, listing them, using Realtime etc. The same as you can with other backends.
But the actual execution happens on dedicated workers.
maiden schooner
Thanks. i don't really understand the answer. What does it mean the actual execution is on dedicated workers? Where do we put the code? Is there an example on how to use trigger.dev v3 on Cloudflare Workers? The example in Hono was from version 2.
shadow grail
We don’t have a specific guide for Cloudflare Workers, v3 works across all runtimes and frameworks. So you can just follow the quick start https://trigger.dev/docs/quick-start
maiden schooner
so what does this mean? "But the actual execution happens on dedicated workers."
shadow grail
You write your tasks alongside the rest of your code but when you deploy they’re deployed to our infrastructure that is built specifically for long running tasks and allow full Node.js dependencies with no timeouts.
This is the thing to read https://trigger.dev/blog/beta-to-latest-announcement
maiden schooner
so when we deploy to cloudflare workers this happens automatically? Is there anything we need to do specifically?
shadow grail
You can set it up with CI, there’s a section in the docs here https://trigger.dev/docs/cli-deploy