Ah nvm, it just accepts a single build and deploy command, so useful only for very basic things.
Ah nvm, it just accepts a single build and deploy command, so useful only for very basic things.



not_found_handling = "single-page-application" doesn't seem to quite work without handling in the worker? Am i right about that? You want to bind it and hand the request back to assets to get the correct asset.Also, On a pro account when using the Cache API in a worker, it’s cached in the nearest colo to where the worker is executed from, from what I understand.That's the same for any plan. It's not "the nearest colo to the worker", workers run directly in colos. Cache is all PoP based now though
My question is there any way to cache in a location closer to using that api on the pro plan?no, cache api is only local. What do you mean "closer"? though, closer to what? Maybe you want something like Smart Placement to run the worker closer to your backend?
_headers files to modify static file request headers is not currently supported, right?Cache Rules does not seem to work either,cache-control: public, max-age=0, must-revalidatecf-cache-status headerscross-origin-embedder-policy: require-corp
Transform Rules, the same effect as with Pages can be achieved.

scheduled() I'm doing a request to an API every x minutes, providing the etag from the last request in the If-None-Match header to avoid further computing if the data isn't changed. While this works perfectly locally (api returns 304), when deploying the api is returning a normal 200 with the same etag as the old one, like if it didn't correctly receive it. Is this somehow a problem on my end?observability flag to be added to wrangler@using-keyword-experimental ?



Subrequests are requests triggered by calling fetch from within a Worker. A subrequest that throws an uncaught error will not be counted.But in the limits section it is specified that subrequests also include D1/KV so this is a bit confusing

not_found_handling = "single-page-application"Cache Rulescache-control: public, max-age=0, must-revalidatecross-origin-embedder-policy: require-corpTransform Rulesscheduled()If-None-Matchobservabilitywrangler@using-keyword-experimental#:schema node_modules/wrangler/config-schema.json
name = "cf-worker"
main = "src/index.ts"
compatibility_date = "2024-05-12"
compatibility_flags = ["nodejs_compat"]