`cacheKey` is Enterprise only - if you're referring to `fetch(..., { cf: { cacheKey: foo }});`
cacheKey is Enterprise only - if you're referring to fetch(..., { cf: { cacheKey: foo }});
Voh
KThe Cache API allows fine grained control of reading and writing from the Cloudflare edge network cache.
VOk, for a bundled worker I know its 50ms (on paid) max run time. But in that run time, network waiting time for resources does not count, but I assume there is hidden limit there. Does anyone know what that is?
KThere is no hard limit for duration. However, after 30 seconds, there is a higher chance of eviction.
KKThere is no limit - just that if there is a need to restart the runtime, such as for an upgrade, 30 seconds is your grace period.
VI'm getting
CF-Cache-Status: DYNAMIC. Any way to force it to cache?KDepends - is the website you're fetching using Cloudflare themselves?
VAbout half my calls are the cloudflare api itself (for other products than workers), and the other half is not
HIs there any way we can have build time environment variables for workers? I know there is the runtime one but that won't work in my case because I need the env in one of the imported files which is done at the top before the worker script runs
HLooking for the equivalent of process.env.NODE_ENV in a CRA build, if that helps
KYou can use —define to replace globals at build time with Wrangler?
HI'm getting
Uncaught ReferenceError: ENV is not defined Is this intended for JS files? It seems to just override the actual code, not setting the variable...KIf that's from trying to access
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.HI simply have
WORKER_ENV === 'stage' in a .ts fileHIn my
wrangler.toml I have define = { WORKER_ENV = "stage" }HSo when I build the worker, it would say "stage" is not defined, because it's treating it as a variable name, which doesn't exist
H"stage" should be the variable value
BYou can always fallback to using bundler features.
K
K
Kit's also elided away since
if (false) is dead code so esbuild removes it during minificationKin your scenario, if you want
FOO to be literally replaced with "bar" then it's...K
HGot it. Thanks for investigating, that makes sense 
KThe whole thing could do with more documentation - it has like 2-3 lines of explanation in the commands section of the docs.
It's just https://esbuild.github.io/api/#define under the hood though
It's just https://esbuild.github.io/api/#define under the hood though
KSecrets are supposed to be managed with
wrangler secret put to be stored on edge, and you can use a .dev.vars file for local development & .gitignore thatKYes
KDelete it from wrangler.toml
KYou can just leave comments on what to do
SI'm trying to make API in DART Language with some Dart Package. Is it possible?
KIf it transpiles to JavaScript or targets WebAssembly, maybe?
Khttps://github.com/cloudflare/dart-worker-hello-world just transpiles it to JavaScript
GitHub
Dart hello world for Cloudflare Workers. Contribute to cloudflare/dart-worker-hello-world development by creating an account on GitHub.
Sit gives this type of error
S
wrangler 2.8.0 -------------------
Total Upload: 88.17 KiB / gzip: 18.06 KiB
X [ERROR] A request to the Cloudflare API (/accounts/6df991ac408d850bce9a330af5edea3e/workers/scripts/untitled_api) failed.
Uncaught Error:
at worker.js:405:13 in a
at worker.js:1158:17 in bC
at worker.js:1147:11 in ct
at worker.js:1087:18 in cx
at worker.js:2429:20 in cL
at worker.js:2394:42 in cY
at worker.js:3537:9
at worker.js:3516:9
at worker.js:3531:7 in dartProgram
at worker.js:3539:5
[code: 10021]
If you think this is a bug, please open an issue at:
https://github.com/cloudflare/wrangler2/issues/new/choose
GitHub
GitHub is where people build software. More than 94 million people use GitHub to discover, fork, and contribute to over 330 million projects.
KIt's certainly not a 'supported' scenario so you'd have to read through your generated JavaScript to see where the issue is, or ask the package author if it supports the whole JavaScript transpile step.
KRealistically, normal JavaScript (and TypeScript) or WebAssembly are the only Workers worth using
ZNot one click but https://developers.cloudflare.com/workers/platform/deploy-button/
