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
JavaScript worker accessing secrets store for array
Still got worker exceeded CPU 10ms time limit in Paid plan
[ERROR] Unable to determine module type for application/source-map mime type
[ERROR] Unable to determine module type for application/source-map mime type
[ERROR] Unable to determine module type for application/source-map mime type
From wrangler: 4.16.0 onwards, @cloudflare/puppeteer .connect API does not work on a worker
this.browser = await puppeteer.connect({ browserWSEndpoint: wsEndpoint });
this.browser = await puppeteer.connect({ browserWSEndpoint: wsEndpoint });
Worker Duplicated
wrangler deploy --name="kno2fy-dev-exp"
wrangler versions upload --name="kno2fy-dev-exp"
...
Non-Production Build URLs
How do I set the version/tags/message on deploy?

Issue with Notification Setup for Worker Standard Requests
Production worker keeps trying to use old code from previous build
Production worker - response code 520

wrangler dev --remote: Browser Redirects to Production URL
Any way to change the workers.dev subdomain?

Can the DurableObject `ctx` able be safely used as WorkerEntrypoint `ctx` object?
Adding a type for a secret to worker-configuration.d.ts
"Sorry you have been blocked" via local worker

Prisma + D1 fails when external API returns 429 error in Cloudflare Workers
``
PrismaClientUnknownRequestError: Invalid prisma.userDeposit.create()` invocation:
Error occurred during query execution: ConnectorError(ConnectorError { ...`ReferenceError: XMLHttpRequest is not defined` crashes Next.js API
ReferenceError: XMLHttpRequest is not defined. The API remains in a "crashed" state for a few minutes until (what I assume) the Worker restarts itself. The app's page routes load perfectly fine, but no API routes work at all during these few minutes.
The error message is indicative of a Node.js API support issue: a library I'm using seemingly references XMLHttpRequest under the hood which isn't supported in the Edge runtime. I've suspected it was supabase-js (despite using the custom fetch implementation) . I've since refactored the suspect endpoints to only use fetch and no other third-party libraries, yet the same issue happens.
It's also important to note that even though I have a few endpoints that consistently crash the API, there are many other endpoints (containing both read and write operations) that also use supabase-js and even axios that are called many times throughout the app with no crashing whatsoever. It only happenes with a few specific endpoints. The endpoints that begin failing with ReferenceError: XMLHttpRequest is not defined were previously working before the suspect endpoints were called....Need help getting FFmpeg working on Workers (close, have got it working when running locally)
How can I make requests to my RPC WorkerEntrypoint worker.