👀

I'm using

swc/jest

for transforms so not sure how that factors in.. it claims to be a drop-in replacement

but thanks for the link, this might be useful

does anybody know if it's possible to invalidate caches (either the edge cache or KV) using wildcard or regex?

E.G if I have a list of cache keys like this: domain.com/foobar/123 domain.com/foobar/456 domain.com/foobar/789 is there any way to clear all cache keys that contain foobar?

So interesting, we removed a service binding from the worker and now it deploys

so think there isnt actually a issue and the error is just misleading, essentially the service it was bound to was removed, however the error message doesnt state which worker it couldnt find

Ohh, interesting

found it by luck while refactoring lol

Yeah, definitely make an issue on the wrangler repo for that, I'm sure that error can be improved

Ah yes... seen that issue before

We should improve that, it's confusing indeed

@Vero 🐙 can you shoot this over to the Worker team and get a ticket made (if we don't have one already)?

yep, raisinggg

We should make an internal ticket, it's in the worker service not wrangler after all But ty for raising that regardless

Is it possible and best way to use a worker as a fallback origin within an LB for when displaying a maintenance page if all origins are down?

When using

fetch

cache, is the body limit 512MB for free plan? (although worker runtime memory is 128MB 😐 )

If that's the normal limit then yes

But you don't need to load the whole body into memory, you can just stream it through

imma put the

res.body

to a

flexsearch

index 😗

oh you mean by using stream, the worker can read cache that larger than memory? 🤔

By streaming a Response, you can serve multiple gigabytes to the client without issue

https://developers.cloudflare.com/workers/wrangler/configuration/#triggers The docs claim that the key should be called

cron

which is a

string[]

. But then in the example it uses a key

crons

Good catch, it's definitely

crons

If you want to throw in a PR, that'd be awesome! https://github.com/cloudflare/cloudflare-docs/blob/production/content/workers/wrangler/configuration.md#triggers

Anyone know if Mailchannel's Worker API has limits? Like if I send 50 emails in bulk will there be a problem? Or should I spread them out a bit

TL;DR I'm bulk denying applications and want to make sure I don't hit limits or get them marked as spam 🙂

I have been trying a few reverse/CORS proxies for almost 6 hours now, but all of them lacked some kind of feature i need. Some examples: 1. reflare ( https://github.com/xiaoyang-sde/reflare-template) : no support for dynamic upstreams / per request configured upstreams. Needed for a "cors anywhere" feature". 2. Cloudflare example from docs (https://developers.cloudflare.com/workers/examples/cors-header-proxy/), lacking iframe (if i remember correct) support, 3. A number of gists either lacking iframe support, dynamic upstreams or something similar. Can anyone suggest me the "perfect" reverse/cors proxy for workers? Primarily for cors but if it acts like a "nginx" or "caddy" reverse proxy to my sites, it would be a bonus. Thanks in advance and Have a nice night!

how do I run worker in local dev with my custom domain? use tunnel?