Hello, I've been experimenting with Next.js for pages, but I understand that every visit to a site generated with it will incur a cost in functions (requests) even if its SSG´d. Let's say they don't count as static assets since there is a function call before the page is served that I think that serves primarily to routing purposes. Which framework or page builder do you recommend to avoid this expenditure on requests for static content?
Hi and thanks for your response!! So could you confirm that using Astro I will be able to use "output: hibryd/server", so to build a site that has both static pages and may be some dynamic route/page (to handle authentication etc) and static pages will be served as static assets (no function requests when rendering them)? Maybe its a situation that is only present on next-on-pages...?
I'm having trouble with a pages function. I'm running "wrangler tail" but not seeing output when I hit the function with a curl command. Is there a way to make sure the tail is connected to the right function? I was using a worker at one point but realized I can just use pages functions.
you can either pass in the id or url or deployment, or use --environment production to get the latest production. Or you can tail it via the dashboard under the deployment itself
so in my wrangler.toml I have kv_namespaces with a binding. I must have created that kv_namespace somehow. I vaguely remember using wrangler to do that.
A binding enables your Pages Functions to interact with resources on the Cloudflare developer platform. Use bindings to integrate your Pages Functions …
Wrangler is very much workers first, although functions share the same resources (like kv buckets, r2 namespaces, etc) CF is eventually hoping to converge both pages and workers into one product, a while off though
it was broken for a few mins for sure, we escalated it and they made a retroactive incident, hopefully will get a retro status page as well. There was more talk in 🤖turnstile