m.muiznieks
CDCloudflare Developers
•Created by will smith on 2/7/2025 in #workflows-beta
is `npx wrangler types` supposed to work
Maybe. I just took this approach from the Zaraz, as it does not support the workflows directly (as its based on wranglers 3.19 or something version).
20 replies
CDCloudflare Developers
•Created by will smith on 2/7/2025 in #workflows-beta
is `npx wrangler types` supposed to work
After nr. 4 don't forget
npx wrangler types 20 replies
CDCloudflare Developers
•Created by will smith on 2/7/2025 in #workflows-beta
is `npx wrangler types` supposed to work
20 replies
CDCloudflare Developers
•Created by m.muiznieks on 2/3/2025 in #zaraz
Cloudflare HTTP headers · Cloudflare Fun...
Yes, I actually didn't do anything wrong or different - I just made a KV call with the same function I do on the Zaraz (I would like to move that in front of Zaraz, to reduce unnecessary event calls).
I caught that because I have a function in place that checks between client.url.href and payload.page.url.href - so thats how it surfaced.
Technically the client variable is not 100% necessary, but its too deep integrated in the whole process to quickly get rid of it.
And then a wall of durable object errors appeared.
But maybe I'm just "special." A few days ago I run into issues with workflows as well, but they admitted that it was a bug and probably the fix will be rolled in this week.
4 replies
CDCloudflare Developers
•Created by m.muiznieks on 2/3/2025 in #zaraz
Cloudflare HTTP headers · Cloudflare Fun...
Will take a closer look.
But for now I decided not to use this feature as I hit two major issues - it sometimes pass wrong
client object to main Zaraz worker, where instead of actual client data it consists from the data that is related to Context worker (i.e. client.url is zaraz script url).
And I hit the errors of "Durable object exceeded maximum computing time" at the Zaraz worker.4 replies