My project isn't huge, just Nextjs, NextUI, and swr essentially

I'll move things to a worker and see if that does it

You're probably hitting https://github.com/cloudflare/next-on-pages/issues/47

If I were you with a Next project, I would seriously consider moving to Netlify or Vercel. Their support for Next.js is much further developed and supported unfortunately. I've seen too many people waste hours of their time 😅

got it

If you do continue, I'd definitely encourage you to file any issues on that repo. I just can't really give you any kind of ETA for stuff getting fixed 😅

thanks for the help anyway!

hi guys, been thinking of a page rule caching strategy for a potentially high traffic SPA. Option 1: (as described here in "Best Practice 2"): https://support.cloudflare.com/hc/en-us/articles/360021023712: 1. Cache Everything (to act as catch all for static, anonymous content) 2. Bypass Cache on Cookie (to bypass caching everything if the request has a matching cookie) -> in my case an auth cookie 3. Origin Cache Control (to specify how long Cloudflare should keep the cached resource in our edge network before asking the origin for it again) -> I would call a REST endpoint in Azure which would return a reponse with a header telling CF how long to cache. My data would be in Azure. Regarding nr. 2, since Pages Functions run in front of cache, I was thinking of implementing the protected (auth cookie required) endpoints with Functions (calling the Azure origin, in Functions I could use fine grained cache control there, meaning cache/invalidate cache responses there for logged-in user x) Option 2: Do everything in CF and use Pages Functions, R2, Cache, etc. I'm leaning towards option 2 atm for perfomance/price (particularly egress) reasons. Do you agree?

Is there any documentation on how to install and use npm packages in functions in Cloudflare Pages? There seems to be no documentation on that. How does the

package.json

has to look like? What directory does it go to? The errors when deploying are not helpful at all 😦

You can mark the path "@tsndr/cloudflare-worker-jwt" as external to exclude it from the bundle, which will remove this error

package.json
dist
  index.html
functions
  hello-world.js

I don't think there's any specific documentation, but you'd probably want the

package.json

in your root with a structure like that. Then it should just be as simple as `import`ing them. If you're having trouble, a git repo or something to reproduce the problem would be great 🙂

Pages Functions bypass the Cache Reserve, is there any way to put a Function response behind the Argo Tiered Cache without using a double proxy like Bunny Origin Shield?

Workers run before cache

That cannot be changed

Is there any workaround other than use a double proxy? Maybe a CNAME chain to trick the reverse proxy to treat the Pages origin as external traffic and use the tiered caching?

Thank you. Unfortunately, that doesn't work either. Still getting "You can mark the path "@tsndr/cloudflare-worker-jwt" as external to exclude it from the bundle, which will remove this error.". It looks like the automatic Cloudflare Pages deployment isn't running

npm install

. How can that be triggered automatically?

If you have a

package.json

in the root, Pages CI will run

npm install

automatically.

Can you share a repo or something to reproduce this?

do you have a build command set?

omg I've set that up way too much time ago and forgot that there are these settings per Page. Setting

build command

to

npm install

fixes it.

yeah...

we really need to do something about that

i'd just use

exit 0

for now

Yeah having to set it to something to trigger expected behaviour isn't very ergonomic

A good example project and step-by-step documentation for functions that use packages would be helpful. Anyway, got it solved now. Thanks for the emotional support 😄

Hey! Is it possible to install npm packages in pages functions, and if so, is there a guide to look at somewhere?

Yep! We discussed this a bit just earlier today. It should "just work" 🙂 https://discord.com/channels/595317990191398933/910978223968518144/1061308850390708284

Is there any flags or other configurations that need to be set in order to use env variables in local development? I have set up env variables in the dashboard and they are available in the prod but when developing locally I am stuggling with an error

[pages:err] Cause: Error: getaddrinfo ENOTFOUND undefined

local env variables need to be in a

.dev.vars

file in the .env format like

myvar=myvalue

is there any plan to make pages functions support creating durable objects? currently you have to run a separate worker to expose the DO, and there doesn't seem to be a way around that.

Durable objects are quite special in the way of creating and deploying them.