workers-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
how to upper timeout workers, default
Hey folks, as of late I'm getting a lot
e0701398-a355-4b31-a80b-8bce36e8c13b
)...Is it possible to restrict the
I have a problem, in my office I have a
Thanks @Walshy - after i deploy the

Environment Variables & Secrets
text
environment variable in the dashboard and not on my wrangler.jsonc
Then for some reason, the environement variable just disapeared (or was it the value, I can't remember)
Then, on my production app, all of the sudden, all client got 403 from my API. It turned out the value of a secret
got cleared/emptied without any action on my side. ...IIRC it isn’t running commands for
EMFILE: too many open files
EMFILE: too many open files, open '/opt/buildhome/repo/node_modules/astro/dist/cli/throw-and-exit.js'
I just spent a whole day trying to debug a weird issue with CI deploys.
I have a minimal astro project with 8 pages (total) and a worker.ts file. My worker sends requests from /dashboard to my oracle server, everything else goes to astro static files.
Information about my project...is their documentation for this in the
Change Repo for CI
The `cloudflare:` prefix is used because
cloudflare:
prefix is used because, just like node, these are classes provided by the runtime itself.Can static site content and api backend
👋 I've got a simple list of schedules
`--metafile` flag released in wrangler!
--metafile
flag to the wrangler CLI. This outputs esbuild's metafile, which can then be used to easily analyze your Cloudflare Worker's bundle size!
Update wrangler to v6.15.0 or newer, then simply run: npx wrangler deploy --dry-run --metafile=./meta.json && npx banal -M ./meta.json
(or add to your package.json file as analyze
).
This command uses banal – it's a great tool by fabiospampinato that provides an offline version of esbuild's web analyzer. Makes peeking into your bundle super easy!...
That's the new typegen stuff with
wrangler types
. I'm personally not a big fan of it, but it's where things seem to be moving. I believe it causes more problems than what it sets out to solve - such as no nodejs_compat
, interop with libraries that do need to import from workers-types
and now ending up with duplicate types, etc. so in all of my projects I'm still using workers-types
and defining my Env
manually.will cloudflare move away from bindings