Thank you, I tried that as well, and doesn't work. Did you manage to make it work?
Thank you, I tried that as well, and doesn't work. Did you manage to make it work?
MIF cache busting solves it, you could as well make a custom implementation and call it when/where you need it. I mean, revalidating would give the same effects than creating a "new" fetch (by adding timestamp somewhere, route or headers). Hope someone may explain all this a little bit more or give some clarification/solution (I myself can´t make the cache: no store option to work, and found that only revalidatePath/Tag are the only ways to revalidate a fetch made inside an nextjs project on nexat-on-pages).
KThe only thing I can think of is that in my page.tsx file I import in a 1mb json file. Could that be whats slowing it down?
KIf not, does anyone else know how to trouble high cpu time? (median is about 150ms for me)
Nyes maybe
OYes, if you want a working example run
npm create cloudflare@latest select "Website or web app" and "Next". Uncomment the KV section in wrangler.toml and app/api/hello/route.ts. start dev server npm run devwrangler & @cloudflare/next-on-pages) etc.
Ahttps://github.com/iflamed/hono-react-ssr-shadcn-ui
Sharing this cool project that I found on Hono discord server
All credits to the author
Sharing this cool project that I found on Hono discord server
All credits to the author
GitHub
Template code for Honojs with React SSR and Shadcn-UI which running on Cloudflare Pages. - iflamed/hono-react-ssr-shadcn-ui
AWas investigating to find out why my site was slow in some pages, then today I finally found out why. For some reason making CF cache resulting pages at the edge (by using a Cache Rule) doesn't play well with page streaming: the page is returned only when Next is done rendering the whole page, so TTFB becomes a second and a half instead of milliseconds. Is this a known issue? Is there a config I can operate to have both CF cache and page streaming when not primed?
SYou are a bloody legend. This fixed every weird cache issue we were facing 
Can't thank you enough. I owe you a beer/coffee. Seriously. I think this is important information for Nextjs devs coming from Vercel where distributed, fast caching is the norm, so I've suggested an edit to the framework guide (https://github.com/cloudflare/cloudflare-docs/issues/14231).
Can't thank you enough. I owe you a beer/coffee. Seriously. I think this is important information for Nextjs devs coming from Vercel where distributed, fast caching is the norm, so I've suggested an edit to the framework guide (https://github.com/cloudflare/cloudflare-docs/issues/14231).GitHub
Cloudflare’s documentation. Contribute to cloudflare/cloudflare-docs development by creating an account on GitHub.
FIt looks like I cant use React Server Components with Cloudflare Pages and Nextjs right? At least not If I try to use D1. I need to call
getRequestContext() on the edge and I can only set export const runtime = "edge"; within an api route, right? (Nextjs 14)
Tthat's not true, you can export that const in a layout file and that will affect all pages within it
Tactually I do export that const in various places like my D1 functions folder
Fdo you use
and thanks for the hint with the layout, I didn't try that one
use server within the files in your D1 folder? and thanks for the hint with the layout, I didn't try that one
TI only use "use server" for server actions, and I use server actions when I need to fetch or update data from client components. Since I cannot use D1 bindings directly from client components, I use server actions to forward requests to the file that interacts with D1.
Server actions are all exported functions that you have in a file that begins with the "use server" directive, and adding this directive at the top of the file means that you cannot export any other thing except for async functions, not even the "export const runtime = 'edge'" - so they have this limitation, which I believe is intented.
Server actions are all exported functions that you have in a file that begins with the "use server" directive, and adding this directive at the top of the file means that you cannot export any other thing except for async functions, not even the "export const runtime = 'edge'" - so they have this limitation, which I believe is intented.
Ftysm! I think I didnt understand how all these pieces work together, now I've managed to call my d1 db without any problems. I really really appreciate it your explanation cleared it for me
TI'm glad to be helpful!
GHey! Anyone aware if I could use Cache API (caches.default) in next-on-pages project's middleware file?
Cno, pages bundles it all into a single worker file, and the limit is on that
Mhmmmm kk
MI mean that's not a limitation for me rn, the limitation is prisma x supabase isn't compatible on the edge yet 
but hopefully when/if that happens I'll be back on CF
but hopefully when/if that happens I'll be back on CF
VI made an action
In dev (localhost) it works. When deployed to CF, it fails request and returns 404 response with not found html page.
If on first line of action I
updateItem(id, value) that is called in client component via onClick.In dev (localhost) it works. When deployed to CF, it fails request and returns 404 response with not found html page.
If on first line of action I
console.log("updateItem starts"), it doesn't even appear on CF logs. And what is strange, on CF logs there are multiple calls to the url (2-6 extra requests on average).VI heard that if action throws in nextjs, then it returns 404 page. But not even a single console.log() being pushed is a bit strange to me.
Midk if it's anyhow relevant to you but I've had an issue before w/ cf where I was importing an action directly from a client component - which in theory is safe but it started working again once I passed it in from a server component, so might be worth checking if that helps?
MI actually usually prefer passing it via server components 
might just be a me thing tho
might just be a me thing tho
TI'm going to move that to pages-help sorry
Lhttps://developers.cloudflare.com/workers/observability/logging/ i send mine to axiom via a tail worker
Cloudflare Docs
Use different methods of logging throughout the entire software development lifecycle of your Worker project.
VIs it me or Next is "handling" errors instead of actually throwing anything useful to logs?
Vi.e. I have server action that throws, but logs are OK as request returns 404 html and no other errors available in tail
NHey, Is there a way to access KV, D1 etc from local with nextjs ?
Nthe bindings are always null when i do next dev
DCould not find a declaration file for module '@cloudflare/next-on-pages/next-dev'. on import { setupDevPlatform } from '@cloudflare/next-on-pages/next-dev' in next.config.mjs. Any suggestions?
Lis there a billing or speed difference in calling a worker via service binding vs calling via fetch+custom.domain for worker? Provided i am using next-on-pages
Wservice bindings will be faster
Wboth will charge an invocation (but service bindings won't in the future)
LAccording to the docs, i have to use wrangler pages dev if i am using a service binding for the worker(defined in .toml)
So if i use next dev, is it correct to assume the worker would be unavailable?
So if i use next dev, is it correct to assume the worker would be unavailable?
HHi, I have next.js with zero trust + workers as API
How i can access current signed user's email in next.js and worker?
My current hint is to decode frontend cookie in worker and hopefuly will get that email and send it back to frontend in response? Some endpoint like
How i can access current signed user's email in next.js and worker?
My current hint is to decode frontend cookie in worker and hopefuly will get that email and send it back to frontend in response? Some endpoint like
GET /user thats is requested on initila page load
DHey! What's median cpu time after using it?
And are you able to use it since it always hits the cpu time limits.
And are you able to use it since it always hits the cpu time limits.
L@cf-wasm/og didnt work for me either on local dev
I ended up using the vercel one as well.
I ended up using the vercel one as well.
DHow are you importing it?
Limport * as og from "@cf-wasm/og/next";
Lwas giving me webpack errors
DCan you show the error?
LI have part of the error still in clipboard since i no longer have it installed.
not sure how much it would help but here it is
not sure how much it would help but here it is
Lit seems other people had the same issue but with vercel/og as well so might not be your library
https://github.com/vercel/next.js/issues/44003
https://github.com/vercel/next.js/issues/44003
GitHub
Verify canary release I verified that the issue exists in the latest Next.js canary release Provide environment information Operating System: Platform: win32 Arch: x64 Version: Windows 10 Pro Binar...
MWhen i am building my dynamic routes with SSG it is forcing me to use edge even though i have set
as mentioned in the documentation.
here is https://github.com/cloudflare/next-on-pages/issues/751 to github issue which is posted by someone else
as mentioned in the documentation.
here is https://github.com/cloudflare/next-on-pages/issues/751 to github issue which is posted by someone else
GitHub
next-on-pages environment related information myproject@0.1.0 deploy npm run pages:build && wrangler pages deploy myproject@0.1.0 pages:build npx @cloudflare/next-on-pages 
@cloudflare/ne...
@cloudflare/ne...MAny help?
Cmy next js project building fine locally, but on cloudlfare, it keeps on building for hours, but does not finish
