Peter Belbin
CDCloudflare Developers
•Created by Peter Belbin on 8/14/2023 in #workers-help
How does one define a Wrangler project to be independent of the containing monorepo?
I have a monorepo, but want to define within it, Wrangler 3 projects that stand alone. ie: I don't want the module resolution to ascend above the Wrangler project base folder. Is there a way to do that?
2 replies
CDCloudflare Developers
•Created by Peter Belbin on 8/8/2023 in #workers-help
Wrangler 1.x allowed CF_ZONE_ID to be set as an environment variable. Does Wrangler 3.x ?
Wrangler 1.x allowed CF_ZONE_ID environment variable to be set to provide the zone ID. Does Wrangler 3.x allow similar to be done? Is it directly supported, or am I required to configure a Zone ID route within the TOML config file?
7 replies
CDCloudflare Developers
•Created by Peter Belbin on 8/8/2023 in #workers-help
Wrangler 3 'dev' in a Yarn monorepo using Plug'n'Play
Has anyone had success using Wrangler 3.x 'dev' in a monorepo that uses Yarn's Plug'n'Play? If yes, what's the magic sauce I need to add? Trying to use it within monorepo just yields errors as described here: https://github.com/cloudflare/miniflare/issues/591
1 replies
CDCloudflare Developers
•Created by Peter Belbin on 5/24/2023 in #workers-help
Wrangler 3 Worker with KV that caches static content
When using
wrangler deploy to deploy an update of an existing worker that itself uses KV to cache assets, at what point do the old KV assets get deleted? eg: over the span of a day, 3 updates get pushed via wrangler deploy. If I don't use wrangler delete, do previous iteration KV assets just fall out due to expiration of TTL or expiration time being reached, or is something also deleting them immediately?1 replies
CDCloudflare Developers
•Created by Peter Belbin on 5/23/2023 in #workers-help
What happened to CF_ZONE_ID in Wrangler 3?
I see with current Wrangler documentation a mention of 'Zone ID route' (https://developers.cloudflare.com/workers/wrangler/configuration/#zone-id-route) in the config file, but, for security reasons, we don't want the information stored in flat files in any case. I see here (https://developers.cloudflare.com/workers/wrangler/system-environment-variables/#supported-environment-variables) that dynamically defining CLOUDFLARE_ACCOUNT_ID & CLOUDFLARE_API_TOKEN appear to be the go-forward environment variables to use with
wrangler deploy, but, I don't see in the documentation any mention of CF_ZONE_ID or a new CLOUDFLARE_ZONE_ID being supported. Is it? Or, is there some other thing that should be done instead? Please advise.4 replies