workers-and-pages-help
pages-help
general-help
durable-objects
workers-and-pages-discussions
pages-discussions
wrangler
coding-help
kv
🦀rust-on-workers
miniflare
stream
general-discussions
functions
zaraz
⚡instant-logs
email-routing
r2
pubsub-beta
analytics-engine
d1-database
queues
workers-for-platforms
workerd-runtime
🤖turnstile
radar
logs-engine
cloudflare-go
terraform-provider-cloudflare
workers-ai
browser-rendering-api
logs-and-analytics
next-on-pages
cloudflare-ai
build-caching-beta
hyperdrive
vectorize
ai-gateway
python-workers-beta
vitest-integration-beta
workers-observability
workflows
vite-plugin
pipelines-beta
containers-beta
wrangler.jsonc: Unexpected secrets_store_secrets
Unzipping a large (500mb - 2gb) zip file
Waiting in worker
How to export classes with Astro?
dist/_worker.js/index.js but there's no way to extend what is exported from this file.
Has anyone else experimented with this and has more ideas to share? Otherwise I might try to open an issue on the Astro repo....
Workers Sentry integration hasn't been working for a year.
[ERROR] Error: COOKIE_SECRET is not defined. A secret key is required for signing cookies. -

Trying to add a cron job to my worker.
Rate Limiting API open beta feedback
Error: Failed to load external module cloudflare:workers: Error: Cannot find module 'cloudflare:work
Workers performance alerting
Bindings are not being autocompleted in React Workers Static Assets example
wrangler.jsonc
```json
/**...Service Bindings on NextJS
wrangler types to generate types, have the latest versions of everything. But whenever I make a call to getRequestContext() I get an error saying that the Cloudflare Request Context can't be loaded.
The other challenge I've got, is that when I set export const runtime = edge I get another error saying
```...How to manually trigger a cron job worker?
silly question about workers billing

Help migrating from Vercel to Cloudflare Workers
Emulating R2 locally
By default wrangler dev runs in local development mode. In this mode, all operations performed by your local worker will operate against local storage on your machine.
I have a worker pulling files from R2, so no problems there. Also the wrangler deploy is quick, so generally I have no need of local storage. I am curious however what "operate against local storage on your machine" means. Is the general idea that we will setup env.BUCKET_NAME to point to some local folder to make this work? Does the R2 get (e.g. env.BUCKET_NAME.get()) somehow grok this local filesystem link?...Uncaught Error: No such module "node:process"
compatibility_date = "2024-09-23" in wranget.toml...."Update name in Wrangler configuration file to match deployed Worker" even though name is the same
Unable to Authenticate request with 10001 error code
