Cloudflare Developers

CD

Cloudflare Developers

Welcome to the official Cloudflare Developers server. Here you can ask for help and stay updated with the latest news

Join

I m getting

I'm getting ```bash service core:user:chainfuseapi-plugins-rss2json: Uncaught Error: Dynamic require of "node:stream" is not supported at index.js:1:383 at index.js:18:4350...

has anyone managed to get itty router v4

has anyone managed to get itty-router v4 types working with cloudflare's worker types? the main issue appears to be that both libraries have bespoke typings for Request and Response

can you make a doc issue

can you make a doc issue?

fancy 100 agree there is something in

<a:fancy_100:1092953135552667708>% agree, there is something in the works that means inactive DOs won't get charged

The plugin documentation

The plugin documentation? You're using normal git integration, added the html contact form as is (needs the data-static-form-name attribute to be set to anything), you have the functions folder in your root (not in your output directory) with the _middleware.ts file, you can see in build logs under the functions tab, the middleware listed under route configuration?...

but i get a warning abt cloudflared when

but i get a warning abt cloudflared when running a normal apt update anyway lol

cors issue

how can i fix this issue? "from origin 'http://127.0.0.1:5500' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

Possible!?!? - Merging Response Headers and Response Body

Can I get some help merging these two functions into one please? ``` if (STUFF) { response.headers.set(...

Crawler Detection in Cloudflare Worker

Can we revisit this? Any way to detect IF crawler using cloudflare worker on PRO plan?

On a Cloudflare Pages site on a custom

On a Cloudflare Pages site (on a custom domain), I'm making an API request to a Worker (on a custom domain) via fetch(), with cache everything and cachettl set. The response object has some Cloudflare headers on it - cf-priority, cf-ray, server - but no CF-Cache-Status. I was expecting to see that to verify if the request was cached or not. What have I missed, please?...

I was wondering if it is possible to

I was wondering if it is possible to pipe an (image) stream into FormData? I currently have this setup: ```ts const { readable, writable } = new TransformStream(); req.body.pipeTo(writable); ...

I m running into issues trying to

I'm running into issues trying to consume a enscripten-built WASM npm package from a JS worker. are there any examples out there? i see a couple articles from 2018, but they don't seem accurate or focused enough

Probably been discussed a lot but any

Probably been discussed a lot, but any chance worker subrequests can reach other ports than 80/443? The use case is connecting to an external ClickHouse or ElasticSearch database, typically hosted on port 8123 or 9200, without having to have an intermediary router. Tx
They can't unfortunately
Sorry, for digging something up from a couple months ago, but I just stumbled upon this and it seems to blow up my plans for using CF Workers... ...

Stripe

I saw that and it's incredibly exciting. I haven't tested it yet though

Durable objects would be ok for

Durable objects would be ok for matchmaking at a small scale but at larger scale durable objects will quickly start to have some issues that will be pretty complex to try and solve. I would personally recommend using a service dedicated to matchmaking and hosting on an actual server 🤷

Merging Two Workers Together

Need some help merging two worker scripts together. One is a redirect and another alters CSS. Both are working when unmerged. Can someone please help me?

šŸ› BUG: Doing fetch requests in a Worker...

Hi, I have updated my workers and they are using 2.8.1 and now, when I do a env.SERVICE.fetch(request.clone()) it stalls with a " TypeError: Cannot construct a Request with a Request object that has already been used." And it was working before, both in local and deployed in CF....