Lovely

This is kinda cool, so if you keep old compatibility date then new updates technically can't break your worker.

yeah, that's why they exist!

it's such a simple yet elegant solution

you're basically just saying: "it worked during this date"

Yeah thats what theyre for very awesome feature

But can performance also improve if you use the newer compatibility date?

Compatibility dates are only for breaking changes

All other changes are applied regardless of your compat date

Thanks

If I call a other worker from the middleware of pages using service bindings, thats counted as two worker invocations right (when using bundled mode)?

Yep

ok thanks! Ill then just directly go to the worker 🙂

It’d be two invocations either way if you mean that you’ll just use normal fetch

hey all - trying to integrate a node/wasm package but getting "Dynamic require of ... is not supported"

any idea how to work around?

Sounds like /

@kian I meant that I could also call the worker directly from the page instead of going thru the middleware. Would same me a request that way 🙂

@kian appreciate the pointer - CJS plugin converted problem from require to top-level await ?

(am already using ESM as an output format)

Im not sure if i should use custom domains or routes what if i want my worker to return something to this url: api.mydomain.xyz/uptime

Custom Domains are recommended if the worker will be the only thing on that subdomain, i.e api.mydomain.xyz is just to the worker. If you have an existing origin on api.mydomain.xyz, you have to use routes, and you could create a route just for that path to that worker.

* It's slightly more complex then that, you could use a route to cover everything on a hostname and then manually create a dns record for it (using 100:: for originless setups), but Custom Domains make it easier and take care of the DNS side for you, and provision you an adv. cert (which you can delete if you want)

i am using the cloudflare stripe library

and today i am noticing something scary, trying to list out the payment methods but getting the following error: stripe.setMaxNetworkRetries is not a function

const stripe = Stripe(env.live_stripeKey, { 
            httpClient: Stripe.createFetchHttpClient()
 });
 stripe.setMaxNetworkRetries(2);

Maybe I had not been paying attention, but is that a new issue?

Random guess, not looked at the library - shouldn’t it be Stripe with a capital S?

i'm setting the const to lowercase stripe

it used to work