Because vercel decided to in their build output. As I'm thinking about it, I recall seeing some regex in next-on-pages for this specifically, so i'll go yoink that for now

But thanks for that clarification, I didn't realise they all end up compiled together at the end of the day.

Does that mean the workers size limit applies to all function route files combined together, or is that size limit per function file?

When they're combined together, yep

When you're using the

/functions

folder, they're all bundled up together into a single worker.js - the 'Advanced Mode' is where you just write your own

_worker.js

and that's effectively what framework adaptors do

It's worth noting that the size limit is after gzipping

You can also normally do `--minify`/`minify = true` with Workers but I don't think the Pages commands expose that

Oh man

I was going to try and be all clever and have everything done with a separate function file for each route in nextjs like vercel's uses, instead of one big _worker.js file that next-on-pages does

I feel like that is something that should be clearer in the docs, because I didn't realise that at all when I was skimming them earlier

I believe Vercel does the same thing, you just don't see it because it happens on-platform.

At least for Edge Functions

I guess so

Because afaik, Vercel is also limited by the 1-5 MB Worker size limit, just like everyone else.

Just strikes me as odd that they'd output all the fluff like that if they're not going to consume it like that

and by fluff i mean all the stuff that duplicated across each file

@Better James , I had a similar reaction when I learned it all got bundled up together. However, I don't really think about it from day to day because it's hidden from me and I get this nice file system router functionality. That said, I'm not sure what you mean by "stuff that [gets] duplicated". The boilerplate is as little as one line per file in my experience and rarely more than a few lines. When it is, I break it out into a helper file that gets imported into all Functions that need it.

In the case of next on pages, there's a lot of duplicate code per route at the moment is the point that was being made afaik

I was looking specifically at the vercel output when building nextjs, and each function route for each page that vercel builds includes all the code needed for said page. You can in theory run each page completely separately of any other with its built function. So, when I was referring to duplicated code, it's stuff like the manifests, core react stuff, core nextjs stuff, core build stuff that is in each file so that each can run completely independently of another

Such as https://github.com/cloudflare/next-on-pages/issues/47

If I was writing my own functions it would be a completely different case, but in this instance I was looking at what vercel builds to see if I could leverage it in a way different to next-on-pages. Unfortunately, that misunderstanding means I can't

is it possible to fetch an image and then insert it with HTMLRewriter? as a blob, I suppose

I guess it'd be some variation of

hmmm... I'm assuming createObjectURL doesn't work with workers

is that meant to be an address to a local file?

not quite sure how to make this work

It indeed does not exist in Workers

Welp

oh maybe base64 encoding the image