BI was trying to do this with server actions, therefor don't really need the fetch but I guess I might need to
JThat is just to dedupe function calls essentially
JI haven't read about revalidatePath applying to that so I'm not sure if it should or not tbh
BYea true
JBut I don't see how that would persist for you to be able to revalidate it anyway between requests
JThe only cache that persists between requests is the fetch cache
BI think atm none of my requests gets cached, I believe thats the issue
BYea
BI'm gonna try to use fetch and see if that works, don't really understand why they brought server actions if you need to use fetch for the cache
PCan someone provide a working example of Nextjs 14 working with supabase? I've gotten auth mostly working but can't figure out basic queries
JNever used supabase so I don't have an example, but are there any errors that you're running into?
FHello,
I got error on vercel/og while deploying to pages
I got error on vercel/og while deploying to pages
⚡️ Completed npx vercel build.
15:03:21.826 ⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/opt/buildhome/repo/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/opt/buildhome/repo/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
15:03:21.864 FinishedF⚡️ Unexpected error: ENOENT: no such file or directory, copyfile '/Users/usr/Documents/jsfun/nop/.vercel/output/functions/api/og.func/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm' -> '/Users/usr/Documents/jsfun/nop/.vercel/output/static/_worker.js/__next-on-pages-dist__/wasm/wasm_ef4866ecae192fd87727067cf2c0c0cf9fb8b020.wasm'
AI would try removing the .vercel and .next directories. That should fix it.
FNot working, also tried clear the cache still failed.
ARemove node_modules and the lock file for your package manager and run the install command
FYeah did that couple time, I assume the lockfile was broken. After rebuild then I push back to git still failed to deploy.
Fremoved the og function, worked fine
JThanks. Any advice on how I can troubleshoot and or reduce memory usage in build step?
If not, are there guides anywhere on how to upload to pages from local after building? I tried uploading the .vercel folder but the generated cf pages url 404s, I probably made a mistake
If not, are there guides anywhere on how to upload to pages from local after building? I tried uploading the .vercel folder but the generated cf pages url 404s, I probably made a mistake
JAfraid I don't. Regarding the other part though, you can use wrangler to deploy your application with
npx wrangler pages deploy .vercel/output/static
Jsounds like a potential issue with a library you use or something, or maybe a nextjs bug(?) or caching issue if you have caching in front of pages
BFriends don't let friends use Next.
JOk
JSounds like you're taking an issue with Next.js' dev server? If so, that'd be something to raise with next.js I think
JWhat are your routes doing?
DTysm for the
getRequestContext utility.
DIs
caches field (Cache API) accessible?DI am getting this build error when i try to import wasm
Dno it is not... 
I guess we could support that...
although they, in production are just available from the global scope (and in dev you could check if
I guess we could support that...
although they, in production are just available from the global scope (and in dev you could check if
caches is or not on the global scope?)DPS: we currently in the
(we just provide a no-op implementation)
getPlatformProxy utility (used by next-on-pages under the hood) don't have a local dev support for caches: https://github.com/cloudflare/workers-sdk/issues/4879(we just provide a no-op implementation)
DI've already heard of this issue: https://github.com/cloudflare/next-on-pages/issues/39#issuecomment-1939591927
I imagine it's a bug in the next-on-pages build process, I'll have to look into it soon... would you happen to have a minimal reproduction?
I imagine it's a bug in the next-on-pages build process, I'll have to look into it soon... would you happen to have a minimal reproduction?
DYep, I am currently doing that. Btw 
getRequestContext made things easier Dah cool! 
By the way, given our
would that be convenient for you? (I guess it'd save you the trouble to check if
By the way, given our
next-dev hacks we can actually easily make it available during dev too... I can easily open a PR for that, but again the no-op implementation provided by getPlatformProxy is currently the best I can offer would that be convenient for you? (I guess it'd save you the trouble to check if
caches is or not on the global scope)DYes, something is better than nothing 
DI shall provide the minimal reproduction for this issue later.
Thank you
Thank you
DAwesome, thank you very much
SHey! I'm trying to return CSS in the <head> my NextJS app using the experimental-edge runtime so there isn't a flicker on load. This works fine when building statically, but it's not working when using SSR on experimental-edge . Has anyone else ran into this issue?
BI tried when using fetch and still no luck. When looking at some pull requests of next-on-pages previously revalidatePath/next cache and caching wasnt supported yet. Could you confirm that it is now?
JYes we implemented support for the fetch cache a long time ago. Please send code snippets of what you're doing
BYea i just found the pr, sorry for that. I will provide code snippets tomorrow
DThanks
MHas anyone here successfully ran a next pages app with a D1 db locally?
I did follow this setup and configuration: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application
Unfortunately I am not having any luck getting this to run.
I did follow this setup and configuration: https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/#use-bindings-in-your-nextjs-application
Unfortunately I am not having any luck getting this to run.
CTrying to determine if SSR pages are caching correctly... Should I be seeing
cf-cache-status