It is all a single worker. Putting these all into like 20 different workers would be much more compl

It 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?

WWalshy It is all a single worker. Putting these all into like 20 different workers woul...

ethereon•8/29/24, 5:23 PM

won't it get clogged and stuff?

ethereon•8/29/24, 5:23 PM

like for a big app

WalshyOP•8/29/24, 5:24 PM

clogged how?

Smarter•8/29/24, 5:58 PM

Hoping someone has an idea on what I can do here

:

pages-helpDeploying Page Functions with Wrangler

WWalshy clogged how?

ethereon•8/29/24, 7:14 PM

Too many requests

WalshyOP•8/29/24, 7:15 PM

Nope

WalshyOP•8/29/24, 7:15 PM

Workers run everywhere so the chance of overloading a single one is very very difficult but even then we'll just spin up another

WalshyOP•8/29/24, 7:16 PM

Workers are infinitely scalable and power a lot of Cloudflare internals at this point, if we can handle our traffic - we can handle yours :p

WWalshy Workers are infinitely scalable and power a lot of Cloudflare internals at this ...

ethereon•8/29/24, 7:18 PM

Oh 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?

WalshyOP•8/29/24, 7:19 PM

any server-side code is strictly server-side

ethereon•8/29/24, 7:19 PM

So the honk dependency won't be sent to the client, right?

ethereon•8/29/24, 7:19 PM

Hono

WalshyOP•8/29/24, 7:20 PM

not unless you explicitly send to the client

ethereon•8/29/24, 7:20 PM

I am just a little concerned about the JS bundle size is the thing

WalshyOP•8/29/24, 7:20 PM

10 MB compressed is quite hard to hit

WalshyOP•8/29/24, 7:21 PM

Your 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

WWalshy Your actual size is like 30 MB+ to hit that which is a very large JS app - if yo...

ethereon•8/29/24, 7:28 PM

So 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

ethereon•8/29/24, 7:28 PM

Which is why I'm worried about bundle size

ethereon•8/29/24, 7:29 PM

I do try to avoid react whenever I can however

ethereon•8/29/24, 7:29 PM

Is it a good idea or should I split into multiple workers?

WalshyOP•8/29/24, 7:31 PM

I 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

ethereon•8/29/24, 7:32 PM

I would prefer to stay as 1 repo and tightly couple the logic together

WWalshy I think you're probably overly worrying about size, I have an astro react site +...

ethereon•8/29/24, 7:33 PM

I'm still kind of newish to web dev so by dependency management you mean like what goes in regular dependencies vs devDependencies right?

Eethereon I'm still kind of newish to web dev so by dependency management you mean like wh...

Hello, I’m Allie!•8/29/24, 8:08 PM

More that you only add dependencies you actually need

datashaman•9/1/24, 3:30 PM

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.

Ddatashaman 👋 I have a NuxtJS project hosted on Cloudflare Pages. I have the need for an ad...

Hello, I’m Allie!•9/1/24, 5:24 PM

When using #next-on-pages, you have to use Next’s API routes, you can’t use Functions yourself

HHello, I’m Allie!When using #next-on-pages, you have to use Next’s API routes, you can’t use Func...

datashaman•9/1/24, 5:43 PM

i 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.

Hello, I’m Allie!•9/1/24, 6:23 PM

Oh, Nuxt

Hello, I’m Allie!•9/1/24, 6:23 PM

Oops, sorry

Ddatashaman i went for a beer and realized that the nuxt adapter (or whatever) must be using...

Hello, I’m Allie!•9/1/24, 6:24 PM

Wait, remind me again why you need Advanced Mode?

HHello, I’m Allie!Wait, remind me again why you need Advanced Mode?

datashaman•9/1/24, 7:06 PM

i 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

[Object object]

[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

Ddatashaman i am streaming OpenAI responses from AssistantStream, reflecting them into a Re...

Hello, I’m Allie!•9/1/24, 7:20 PM

Am I missing something? That just says the Request context, not specifically Advanced Mode

HHello, I’m Allie!Am I missing something? That just says the Request context, not specifically Adv...

datashaman•9/1/24, 7:25 PM

the 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...

Ddatashaman the way i read it is it can only be run inside a fetch handler function, which y...

Isaac McFadyen•9/2/24, 12:46 AM

Functions based routing is still inside a

fetch

fetch

handler.

Isaac McFadyen•9/2/24, 12:47 AM

They 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

fetch

handler generated internally by Pages.

IIsaac McFadyen They just say that to mean that you can't do it *outside* of the fetch handler, ...

datashaman•9/2/24, 3:51 AM

thanks for the help, I managed to get it working with a server route!

jjjrmy•9/3/24, 9:26 PM

if I'm getting this error, what should I do?

Cannot bundle Node.js built-in "crypto" imported from "../node_modules/oauth/lib/oauth.js". Consider disabling ssr.noExternal or remove the built-in dependency.

Cannot bundle Node.js built-in "crypto" imported from "../node_modules/oauth/lib/oauth.js". Consider disabling ssr.noExternal or remove the built-in dependency.

I'm using Astro, if I add

crypto

crypto

in my

vite.ssr.externals

vite.ssr.externals

, then it doesn't error on build but then says the export is missing when I try to use it.

jjjrmy•9/9/24, 10:34 PM

[commonjs--resolver] [plugin vite:resolve] Cannot bundle Node.js built-in "util" imported from "../node_modules/knex/lib/dialects/sqlite3/index.js". Consider disabling ssr.noExternal or remove the built-in dependency.

[commonjs--resolver] [plugin vite:resolve] Cannot bundle Node.js built-in "util" imported from "../node_modules/knex/lib/dialects/sqlite3/index.js". Consider disabling ssr.noExternal or remove the built-in dependency.

jjjrmy•9/9/24, 10:34 PM

https://blog.cloudflare.com/more-npm-packages-on-cloudflare-workers-combining-polyfills-and-native-code/

Samantas5855•9/13/24, 5:11 PM

is rust more performant than js for pages functions?

James•9/14/24, 12:31 AM

It 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.

James•9/14/24, 12:31 AM

For 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.

paulcq6173•9/16/24, 2:05 PM

Is 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.

Ppaulcq6173 Is cloudflare pages function work with Next.js? I set up /functions/api/test.ts ...

Hard@Work•9/16/24, 2:07 PM

Are you using #next-on-pages? If so, you need to use Nextjs's server actions thing

paulcq6173•9/16/24, 2:09 PM

Yes, I am using @Cloudflare/next-on-pages with my project.

Ppaulcq6173 Yes, I am using @Cloudflare/next-on-pages with my project.

Hard@Work•9/16/24, 2:10 PM

Yeah then you want to use https://nextjs.org/docs/pages/building-your-application/routing/api-routes

Routing: API Routes | Next.js

Next.js supports API Routes, which allow you to build your API without leaving your Next.js app. Learn how it works here.

paulcq6173•9/16/24, 2:14 PM

I am using App Router mode, so this is the reason that cause pages function not work?

Ppaulcq6173 I am using App Router mode, so this is the reason that cause pages function not ...

Hard@Work•9/16/24, 2:15 PM

I don't think so. If you use SSR of any kind with Next, then you need to use Next's API system instead of Functions

[commonjs--resolver] [plugin vite:resolve] Cannot bundle Node.js built-in "util" imported from "../node_modules/knex/lib/dialects/sqlite3/index.js". Consider disabling ssr.noExternal or remove the built-in dependency.

It is all a single worker. Putting these all into like 20 different workers would be much more compl

Similar Threads

Similar Threads

Similar Threads