For 1 request? Sure For 6 concurrent requests? Not so much
For 1 request? Sure
For 6 concurrent requests? Not so much
For 6 concurrent requests? Not so much
DI don't control that though, this is an incoming request.
KIsolates (of which will handle concurrent requests) are what has the memory limit so you might be able to buffer 25MB but if that isolate gets enough concurrent requests you can run into eviction due to exceeding the memory limit
Gwe went live yesterday with our Fastly to Cloudflare migration and so far working very nicely 
only thing I'd like to improve is that we're doing like ~200 requests a second... thinking I need to make more client-side cache changes to avoid so many requests to the workers
only thing I'd like to improve is that we're doing like ~200 requests a second... thinking I need to make more client-side cache changes to avoid so many requests to the workers
Hhey, can i access my R2 bucket in local mode or is that not possible?
JNot possible in local mode unfortunately. You will have to use to access "real" buckets, KV namespaces, etc.
Him assuming will fix my problem
Hlol i iwas just writing that
Halright thanks
JYep exactly 
Hconsole.logging file returns this. Am I able to get the File name or type in my worker? (file was uploaded through multipart/form-data)
G@hypervz try:
Hgot it working thx
Mi'm not sure if this is the correct channel to ask, but anyone know the status of the workers browser rendering API (https://www.cloudflare.com/lp/workers-browser-rendering-api/)? I have a great usecase for it for a project that I'm working on and would love to get my hands on it :). Seems to be in private beta at the moment.
HHey guys. Ive been in a long and tedious process of migrating our express (node) backend to workers. Ive accomplished a lot but now im stuck in formatting images. Previously, i used sharp (a node library) to convert images from jpg to png and pipe the stream to R2 through the S3 wrapper (which was a one liner). Ive tried to accomplish this in my worker using JIMP, image-js, and other libraries but was unable to get it working (presumably due to the lack of support for the canvas api in workers). How would I go about simply converting a jpg image to png in my worker?
Pimage-js works without canvas on cloudflare workers, what error are you getting
for jpeg encoding in image-js I had to import Buffer and set it to self.Buffer globally.
for jpeg encoding in image-js I had to import Buffer and set it to self.Buffer globally.
EDoes anyone know why is not set in global scope with the flag set? To be able to use NodeJS libraries, especially ones that in top level scope with ESM loading, requires some pretty ugly hacks with importing a "polyfill" type file that imports , set it in the global scope, and then need to make sure it doesn't get tree-shaken out.
Bhey folks, I am a bit confused in which state the browser rendering API is and how to get access?
On the blog (https://blog.cloudflare.com/browser-rendering-open-beta/) it says open beta, but still says "we need to sign up for a wait list" (did that)
What is the process now and whats the usually wait time until we can use it?
Thanks!
On the blog (https://blog.cloudflare.com/browser-rendering-open-beta/) it says open beta, but still says "we need to sign up for a wait list" (did that)
What is the process now and whats the usually wait time until we can use it?
Thanks!
The Cloudflare Blog
The Workers Browser Rendering API allows developers to programmatically control and interact with a headless browser instance and create automation flows for their applications and products. Today we enter the open beta and start onboarding our customers.
Chi, I am new to cloudflare workers....I need code to connect D1 database to workers.
have tried this code
export async function onRequest(context) {
// Create a prepared statement with our query
const ps = context.env.NORTHWIND_DB.prepare('SELECT * from users');
const data = await ps.first();
return Response.json(data);
}
but didnt know how to add NORTHWIND_DB as database connection variable. Can anyone please help
have tried this code
export async function onRequest(context) {
// Create a prepared statement with our query
const ps = context.env.NORTHWIND_DB.prepare('SELECT * from users');
const data = await ps.first();
return Response.json(data);
}
but didnt know how to add NORTHWIND_DB as database connection variable. Can anyone please help
CAre there any other tips for troubleshooting ?
I have a small small script:
And it does almost no initialization at startup, but I cannot deploy it.
I have a small small script:
And it does almost no initialization at startup, but I cannot deploy it.
WYou do any imports?
WWhat have you got in the global scope?
Cyeah, a few imports, just saw a note to move those into the handler, and the first one I moved got me over the hump and I can now deploy
Uif you dont have a head function then yes it would be normal
TI'm migrating an existing worker from service worker to ES module format. Not a huge deal, with one caveat. Before I was accessing environment variables as globals, now they're are in the environment object. Are people just plumbing that environment object through layers of their code or is there a more elegant way to handle things? I'm finding myself adding to a large quanity of my functions just to get access to things where I need them.
HYou can use https://developers.cloudflare.com/workers/runtime-apis/nodejs/asynclocalstorage to plumb variables out around your Worker.
Cloudflare Workers provides an implemenation of a subset of the Node.js AsyncLocalStorage API for creating in-memory stores that remain coherent …
TI see. So I could create an asynchronous context at the top of my fetch handler, pass my environment into it, then gain access to that anywhere in the following asynch code. That's nice.
JHow can I know the CPU architecture and OS platform my workers are running on? In node.js I'd use either and , or and . However, there are no such options for CF Workers.
At most, with , I get and
At most, with , I get and
CWhy do you need to know the architecture and OS? That stuff shouldn’t matter in the code
JI'd like to try importing a native addon (which is platform dependent) into a Cloudflare Worker. The addon would be built with napi.rs
CI don’t believe worker code runs low enough where stuff like arch is accessible. All code runs in workerd which is V8 engine
J(I had the strong suspicion this wouldn't be possible and that I'd have to use WebAssembly instead. I'm just asking here to get confirmation)
HYou don't get to run native anything on Workers. It's either WASM, or JS.
TIs it dumb to run WebAssembly inside a JavaScript worker? I have some shared code in WebAssembly that I'm running in many runtimes, it would be nice to run that inside my existing JavaScript worker
TI'm sure there is some overhead for invoking the WebAssembly runtime. Right now my worker takes about 2ms of CPU time. The algorithm is pretty trivial and already in my JavaScript worker. I just want to replace it with the WebAssembly version so I don't have to maintain this algorithm in multiple languages. Any idea how much overhead the WebAssembly runtime has?
IThe main reason WASM takes longer is that there is no runtime, really (I mean there is but not really). By that I mean if you write some code in Go, or Rust, etc, then the entire garbage collector or standard library has to be shipped with the WASM, which means it takes much longer to boot.
IVersus JavaScript, which can be run directly on a V8 isolate, meaning scripts share the garbage collector etc (isolated in isolates but more shared than WASM)
IPretty much the only way to know is to benchmark yourself with your specific WASM code.
TMy hope was to actually invoke my WebAssembly from inside a JS worker. I'm realizing now this might not be possible? I'm not seeing WebAssembly as part of the Worker runtime. Is that right?
TLooks like v8 supports it, but not sure about the CF version
HIt does. That’s how #
workers-rs works
workers-rs worksTGreat. I'm just getting into it. I rewrote my algorithm in AssemblyScript and compiled to WASM. I'm just about to start trying to use it in my Worker.
JToday I've verified that this is possible!
TAwesome
JI noticed today that req.url seems to be defined to be relative to the routes in your wrangler config, even when you are developing locally.
This has issues when developing locally with libraries like next-auth, since they use the req.url to generate the callback urls.
I'm wondering if anyone here would know of a reason for it to be this way?
This has issues when developing locally with libraries like next-auth, since they use the req.url to generate the callback urls.
I'm wondering if anyone here would know of a reason for it to be this way?
Gtry with though it won't work with
JThat does seem to resolve the issue!
It would still be good to understand why/if this is actually needed if anyone had ideas.
It would still be good to understand why/if this is actually needed if anyone had ideas.
Gdoes anyone know if cloudflare reserves short subdomains for services like workers? (also zero trust seems to have no subdomains available unless you got 3+ chars)