Yeah, is there a way to request for this feature somewhere?
Yeah, is there a way to request for this feature somewhere?
CAlso, curious why is it not present in paid plan when we have the limits on free plan if anyone could explain a bit further it will really helpOn Paid Plans you just pay for each request over the included amount.
You can't raise the free tier's included requests/day, other then by upgrading to Paid
https://developers.cloudflare.com/workers/platform/pricing/
CThere's #workers-feature-suggestions or https://community.cloudflare.com/c/feedback/feature-request/30 on the community forums. I wouldn't hold out hope for it though, virtually no other CF Products have anything like that except Workers Free Tier.
For Standard Billing Model though you can add a CPU Ms Limit per request which can help cap things/make sure a Worker which normally is quick wouldn't take excessively long resulting in a big bill
For Standard Billing Model though you can add a CPU Ms Limit per request which can help cap things/make sure a Worker which normally is quick wouldn't take excessively long resulting in a big bill
Sok thank you
OAnyone knows the Mistral 7b rate limits on workers ai ? I can't find the info ?
Dhow much of a performance hit does
node_compatjust because i am using
process.env
KUse
compatibility_flags = ["nodejs_compat"]It's modules added into the runtime rather than
node_compat
Dthanks!
IIn general you are allowed short spikes above the 10ms limit, but you will run into issues eventually since the median CPU time being above 10ms suggests that eventually you will be limited.
IThe main solutions here are either to reduce your CPU time, if you can, or if you can't (e.g. hashing passwords, running expensive WASM) then you'll need to upgrade to the paid plan or just continue what you're doing (risking being throttled though).
UThe free plan never gets charged. If you were on a paid plan and had a limit set to 10ms you would still get charged the full amount of cpu you use afaik.
BGuys, does turnstile requests consume the Workers' cpu time? Because I benchmarked, and found out that Recaptcha averages 300ms from Cloudflare's servers and sometimes less, whilst Cloudflare Turnstile averages over 400ms from Cloudflare's own servers, so I'm considering switching back to Google Recaptcha if Turnstile is gonna cost that CPU time per request
BOr maybe there's a special way to use turnstile through workers that wouldn't cause that much verification time (like without http requests)?
BOkay, I might be wrong, but quoting Cloudflare's docs:
CPU time is the amount of time the CPU actually spends doing work, during a given request.Does that mean they won't charge for the time where a worker is "halted" (waiting for turnstile to respond)?
CYea, CPU Time doesn't include time you're waiting on responses from fetch requests, CPU isn't active
BAwesome, thank you!
Dhttps://developers.cloudflare.com/workers/runtime-apis/webassembly/javascript/#bundling
The documentation says we can import wasm binaries ending with
But when I import using
Is there any mistake in documentation or am I doing anything wrong?
The documentation says we can import wasm binaries ending with
.wasm.wasm?moduleBut when I import using
.wasm?moduleIs there any mistake in documentation or am I doing anything wrong?
Wasm can be used from within a Worker written in JavaScript or TypeScript by importing a Wasm module, and instantiating an instance of this module …
DOr do I need to add
ruleswrangler.tomlIn the documentation:
This is done using a ~default bundling~ rule which can be customized in wrangler.toml
This is done using a ~default bundling~ rule which can be customized in wrangler.toml
0love it
Ris there a recommended way to handle multiple routes for a worker?
i'm trying to map out an integration i'm working on and not sure if it needs to be 1 worker per URL, or 1 worker per "area" (eg: auth, sales, webhooks), or can be 1 monolith worker - are there any limitations that might steer me to look a certain way?
i'm trying to map out an integration i'm working on and not sure if it needs to be 1 worker per URL, or 1 worker per "area" (eg: auth, sales, webhooks), or can be 1 monolith worker - are there any limitations that might steer me to look a certain way?
EYou can honestly do any of those approaches.
1 worker per URL: assign them routes like
1 worker per area: assign them routes like
1 monolith worker: assign them routes like
so it just depends on what makes the most sense for the dev flow that you want, and you can even have the workers communicate with each other over Service Bindings if need be (https://developers.cloudflare.com/workers/runtime-apis/service-bindings/#service-bindings)
1 worker per URL: assign them routes like
domain.com/thisthing1 worker per area: assign them routes like
domain.com/auth/*1 monolith worker: assign them routes like
domain.com/* or a worker custom domainso it just depends on what makes the most sense for the dev flow that you want, and you can even have the workers communicate with each other over Service Bindings if need be (https://developers.cloudflare.com/workers/runtime-apis/service-bindings/#service-bindings)
EI suppose Workers for each route/path may be harder to develop unless theyre separate components that dont need to interact as a whole
Rthe monolith approach seems to be the sanest approach (well, until it's not)
i'm not too familiar with JS for server stuff, but is there any recommended approach to routing various endpoints for a worker? historically if i've needed an api written in js i'd just use express, but not even sure if that is an option for workers and if i google "cloudflare workers routing example" it doesn't seem to pull up what i'm looking for
i'm not too familiar with JS for server stuff, but is there any recommended approach to routing various endpoints for a worker? historically if i've needed an api written in js i'd just use express, but not even sure if that is an option for workers and if i google "cloudflare workers routing example" it doesn't seem to pull up what i'm looking for
KHono is a small, simple, and ultrafast web framework for the Edges. It works on Cloudflare Workers, Fastly Compute, Deno, Bun, Vercel, Netlify, Lagon, AWS Lambda, Lambda@Edge, and Node.js. Fast, but not only fast.
KThe closest to Express, written for serverless runtimes.
KIt supports chained routes, grouping, etc
Rawesome 
tysm
tysm
JAstro's local development story with Cloudflare is pretty dang good these days
JDocs
Learn how to use the @astrojs/cloudflare SSR adapter to deploy your Astro project.
JTheir adapter adds supported bits of the cf runtime so you can get all the benefits of
astro dev with hmr, etc., but still use Cloudflare features like KV, D1, etc.: https://docs.astro.build/en/guides/integrations-guide/cloudflare/#cloudflare-runtimeJIt doesn't support everything yet, but supports the most popular bindings
](https://cdn.discordapp.com/avatars/732280746022010905/ff8f080750e043696708733a5ed8b403.webp?size=40)
ADoes anyone know how python integration using WASM works on Cloudflare Workers?
KThe Workers template uses Transcrypt, so it's not WASM. There's work being done on the runtime to integrate https://pyodide.org/en/stable/ but you'd be on your own with trying to get that working.
Aok, so right now is there no possible way to run python within cloudflare workers for responses?
KI haven't tried it, so it may be possible, but I haven't seen anyone else do it.
Aok
DI've added
compatibility_flags = [ "nodejs_compat" ] to my wrangler.toml file but the TS server keeps giving this error:
Danyone know a fix?
Dyeah i tried this earlier & restarted the ts server. same error
Doh that works thanks
JI'm trying to dynamically import something in my CF worker, which works when I do:
but whenever I do something like:
I get the error:
but whenever I do something like:
I get the error:
JAnyone know if this is possible?
JThis question was asked once before here:
JBut honestly I'm not sure how to just 'tell Wrangler' based off the response (and link describing bundling) -- if they were referring to using
rules