LHelp me domain pending
I?pings
FPlease do not ping community members for non-moderation reasons. Doing so will not solve your issue faster and will make people less likely to want to help you.
WIt is all a single worker. Putting these all into like 20 different workers would be much more complicated and slow
Whats the concern over a single?
Whats the concern over a single?
Ewon't it get clogged and stuff?
Elike for a big app
Wclogged how?
S
EToo many requests
WNope
WWorkers run everywhere so the chance of overloading a single one is very very difficult but even then we'll just spin up another
WWorkers are infinitely scalable and power a lot of Cloudflare internals at this point, if we can handle our traffic - we can handle yours :p
EOh ok. In that case, I have a question: for vite apps on cloud flare pages, let's say I had Hono working on the server side. Will hono be served in the client side JS?
Wno
Wany server-side code is strictly server-side
ESo the honk dependency won't be sent to the client, right?
EHono
Wnot unless you explicitly send to the client
EI am just a little concerned about the JS bundle size is the thing
W10 MB compressed is quite hard to hit
WYour actual size is like 30 MB+ to hit that which is a very large JS app - if you get that big you probably should split it into smaller ones regardless
ESo I have an Astro project that uses both react and svelte components. React bundle size is huge. Now, due to a single worker scaling infinitely, im debating on mounting a Hono app backend inside Astro, which would definitely simplify things, but that means all the backend dependencies would come as well
EWhich is why I'm worried about bundle size
EI do try to avoid react whenever I can however
EIs it a good idea or should I split into multiple workers?
WI think you're probably overly worrying about size, I have an astro react site + others just plain react and many internal/public sites of ours are react which all are good
SSR or CSR you should be fine with proper dependency management and tree shaking you should be good.
You can split into multiple Workers though, if it makes sense for you to do that then I'd say go ahead
SSR or CSR you should be fine with proper dependency management and tree shaking you should be good.
You can split into multiple Workers though, if it makes sense for you to do that then I'd say go ahead
EI would prefer to stay as 1 repo and tightly couple the logic together
EI'm still kind of newish to web dev so by dependency management you mean like what goes in regular dependencies vs devDependencies right?
HMore that you only add dependencies you actually need
D
I have a NuxtJS project hosted on Cloudflare Pages. I have the need for an advanced mode Worker function (it requires access to the Stream API). I've created the _worker.js file with the required code. My problem is this: where do I put the file in my source repository for it to be deployed and compiled into the pages code? I see mention of the _worker.js being noticed in the output folder (in deployment logs). But... nothing works, function isn't called, the route I expect it to handle returns a 404...I've tried the root of the repo and putting it into public. Neither work.
HWhen using #next-on-pages, you have to use Next’s API routes, you can’t use Functions yourself
Di went for a beer and realized that the nuxt adapter (or whatever) must be using _worker.js to do its work. I remember seeing a whole _worker.js/ folder being generated. So either I need an escape hatch in Nuxt, I need to change frameworks, or I must create a separate worker which does the dirty work. Thanks for the reply! I think I know how to proceed now.
HOh, Nuxt
HOops, sorry
HWait, remind me again why you need Advanced Mode?
Di am streaming OpenAI responses from AssistantStream, reflecting them into a ReadableStream to give to the browser.
this code works fine on local, but when I run it via Cloudflare, the response given back doesn't seem streamy. Contains
so i reckon something in the way nuxt works or in the marshalling of the events is not working correctly.
my read of the docs led to the mention of Stream API use in Page functions which mentions that it only works in Advanced Mode.
https://developers.cloudflare.com/workers/runtime-apis/streams/#common-issues
this code works fine on local, but when I run it via Cloudflare, the response given back doesn't seem streamy. Contains
[Object object] response instead of doing the SSE thing.so i reckon something in the way nuxt works or in the marshalling of the events is not working correctly.
my read of the docs led to the mention of Stream API use in Page functions which mentions that it only works in Advanced Mode.
https://developers.cloudflare.com/workers/runtime-apis/streams/#common-issues
HAm I missing something? That just says the Request context, not specifically Advanced Mode
Dthe way i read it is it can only be run inside a fetch handler function, which you can only do in advanced mode.
without advanced mode it's /functions based routing which does not support streaming? idk...
without advanced mode it's /functions based routing which does not support streaming? idk...
IFunctions based routing is still inside a
fetchThey just say that to mean that you can't do it outside of the fetch handler, like in the global scope. But a Nuxt API route should be inside the
fetch
Dthanks for the help, I managed to get it working with a server route! 
Jif I'm getting this error, what should I do?
I'm using Astro, if I add
I'm using Astro, if I add
crypto in my vite.ssr.externals, then it doesn't error on build but then says the export is missing when I try to use it.J
Sis rust more performant than js for pages functions?
JIt depends what kind of work you're doing, but generally not for most things, no. Workers (and therefore Pages) run V8, so there's always going to be some minor overhead when running anything other than JS.
JFor most things, that overhead will be minimal, and Rust can make some more CPU-heavy operations easier to manage. But for your average web request/response handling, I'd stick with JS unless you have a good reason to use Rust.
PIs cloudflare pages function work with Next.js? I set up /functions/api/test.ts at the root of my Next.js project, then use wrangler to preview, on router /api/test only got 404.
HAre you using #next-on-pages? If so, you need to use Nextjs's server actions thing
