Same as a normal request, `CF-Cache-Status` response header.
Same as a normal request,
CF-Cache-Status response header.CF-Cache-StatuscacheKey is Enterprise only - if you're referring to fetch(..., { cf: { cacheKey: foo }});
There is no hard limit for duration. However, after 30 seconds, there is a higher chance of eviction.
CF-Cache-Status: DYNAMIC. Any way to force it to cache?Uncaught ReferenceError: ENV is not defined Is this intended for JS files? It seems to just override the actual code, not setting the variable...process.env then that won't exist.--define is for, let's say you had console.log(FOO) in your code - you can set it so the built output replaces the global identifier FOO with "bar" as opposed to a runtime variable that you'd find under the second argument to a handler.WORKER_ENV === 'stage' in a .ts filewrangler.toml I have define = { WORKER_ENV = "stage" }

if (false) is dead code so esbuild removes it during minificationFOO to be literally replaced with "bar" then it's...

wrangler secret put to be stored on edge, and you can use a .dev.vars file for local development & .gitignore that[define]
FOO = '"bar"'cacheKeyfetch(..., { cf: { cacheKey: foo }});DYNAMIC