I would assume they are the same as Bundled

If our Cloudflare pages site has functions enabled. Do the hits to the static resources such as html, css, is count towards the function limit (100,000 per day)

You need to grab it from the context parameter.

ts
export const onRequest = async (context) => {
  return new Response(context.env.NEXT_PUBLIC_NHOST_GRAPHQL_API)
}

https://developers.cloudflare.com/pages/platform/functions#environment-variable

Aha, this makes sense

Currently yes

We've just shipped a new

wrangler@alpha

if anyone's feeling adventurous and wants to try out our new static assets server. TL;DR: - much more faithful simulation of how Pages actually serves assets in production, including SPA routing,

_headers

and

_redirects

support - better error handling in your scripts (hopefully no more crashing the entire server!) Let us know how you get on 🙂

Hi, are there any updates about TypeError:

Cannot reconstruct a Request with a used body

, when the POST body is not empty? Thanks

Should be fixed in local dev, but unfortunately still not quite yet in production. We're working on it!

Is there still a 1 MB limit in Pages Functions?

Yes. If you're needing a higher limit, I think you're best to fill this form out: https://www.cloudflare.com/en-gb/larger-scripts-on-workers-early-access/

Pages should inherit your account's limit.

Thanks Greg. To add some more context: we are looking into deploying https://vite-plugin-ssr.com/ on the CF Pages. In regular server environments, it works in a way, where vite-plugin-ssr provides tiny express middleware which grabs generated app files from dist folder and responds with SSR site. For serverless environments they suggest bundling the whole thing to the single file, and before Pages Functions, that was the way to go with Cloudflare. Is that serverless approach still a way to go, or it is now possible to do it without bundling, similar to regular server approach?

Does this change include handling locally persistent KV data?

We introduced persisted KV, DO & cache a couple of releases ago! 🙂 Can't remember if that's in the beta yet, but certainly it's available in alpha.

If your pages are heavy, I think some prerendering makes sense still. I'm not familiar with Vite myself, so can't comment on that specific plugin, but I'd probably just recommend trying it out both ways and seeing how they perform

Hello, I'm would like to use this workers example script inside of my Cloudflare Pages deployment, but I'm stuck on how I would be able to use this with it. Also, is there anyway of making an entire directory ONLY being protected using that script, as I'd like a specific directory eg. /private/* to be protected with HTTP Basic authentication, thanks!

I haven't looked too deeply on that

basic-auth

, but take a look at _middleware: https://developers.cloudflare.com/pages/platform/functions#adding-middleware You should be able to create a private directory with the auth middleware inside and only the functions of that directory or deeper will have it

Thanks! I'll check it out

How would I measure or see the CPU consumption of a function?

Metrics like that are not exposed to the user/programmer for the most part, for security reasons.

How do you know if your function will be rejected due to cpu time?

You can use something like Miniflare, and measure the execution time with DevTools that way. It isn't exactly one-to-one, but it is about the closest you will get.

Alright, although it won't account for cpu difference or worst, i/o 😦

TBH, Miniflare is usually pretty accurate. I have tested a program on Miniflare on 3 separate cloud instance, a Dell Laptop and a pretty powerful desktop, and as long as it can execute a decent sized Node program without struggling, you should get similar results to deploying it to Workers itself.

And if you are worried about I/O, run it on a Cloud Instance, so that your ISP can't be a bottleneck.

It's more like the network between the worker and a 3rd party. The whole thing takes 1225ms on my example, but obviously that's mostly io, not cpu consumption. Anyway thanks 🙏

Unless you are doing something extremely CPU intensive, it is very hard to break the 50ms CPU limit. I think our average worker execution time is like 4ms.

It's not really an intensive task, but it queries a 3rd party with a paginated resource, with potentially any number of pages. But I'm gonna just set a limit and call it multiple times if need be.

Sounds like a very decent solution

Came back from my exam week off, it looks like it resolved itself. Also, you were completely right about the destructuring; someone pushed a bad commit earlier, and I didn't notice 😮‍💨