`"@cloudflare/next-on-pages": "^1.11.0",` `"next": "^14.0.4",`
"@cloudflare/next-on-pages": "^1.11.0","next": "^14.0.4",
JHmm okay, it's possible something might have changed in Next that we need to update something for
JIt does work locally, but I'm running through the next dev command, so I assume there might be runtime API differences with actual deployments? When deployed to cloudflare anything serverside runs with workerd, right?
Jwith
export const runtime = 'edge'
Bwhy are the client components embedded inside the func.js in the functions folder ?
Ntheyre still SSR-ed
BOkay, what can I do to prevent them from being bundled in the functions? "use client" at the parent component?
Blooks like it does the trick, I will reenable them as server components once I get users to pay for the workers plan for 10Mb
TI wonder if you have any news on this? I'm on a very similar situation trying to use RPC locally with next dev
In my case when I run
Using wrangler dev without the remote flag means I can't interact with Vectorize or production R2 buckets..
In my case when I run
wrangler pages dev I can indeed execute rpc method but it also won't work if the worker is running with wrangler dev --remoteUsing wrangler dev without the remote flag means I can't interact with Vectorize or production R2 buckets..
NI don't have any news as I currently don't need to have it working
NIm guessing it needs some kind of workers-sdk issue
TI see, do you know if there is another way for me to fetch another worker's route handler with the same zero-latency that RPC would provide?
TGitHub
Which Cloudflare product(s) does this pertain to? Miniflare What version(s) of the tool(s) are you using? miniflare@3.20240404.0 What version of Node are you using? 20 What operating system and ver...
SHello again!
We've now correctly activated KV cache to handle next.js automatic ‘fetch’ caching. (By activating the bindings settings in cloudflare’s dashboard, and by using ‘cache-force’ when doing our fetch calls as discussed here on discord last week)
We expected calls made during the build of our static pages to populate the KV cache and then be able to use that cached data in our ‘edge’ server rendered pages.
However, the KV cache stays empty after the build. BUT, it populates correctly if we navigate to the server side page.
Is it possible to have build time queries made when building static pages cached to KV correctly? Is there something we could be doing wrong to cause this ?
We've now correctly activated KV cache to handle next.js automatic ‘fetch’ caching. (By activating the bindings settings in cloudflare’s dashboard, and by using ‘cache-force’ when doing our fetch calls as discussed here on discord last week)
We expected calls made during the build of our static pages to populate the KV cache and then be able to use that cached data in our ‘edge’ server rendered pages.
However, the KV cache stays empty after the build. BUT, it populates correctly if we navigate to the server side page.
Is it possible to have build time queries made when building static pages cached to KV correctly? Is there something we could be doing wrong to cause this ?
BRPC has zero-latency and manually requesting has latency? that's very odd, both should be regular requests i believe?
UIf you do a fetch over the internet instead of a fetch on the binding that would be cause for latency. But yes they would both have zero-latency done through binding
THow do I do a fetch on the binding? Is it something like
BINDING.fetch("/some-route", options) ? I couldn't find an example on this
一Please help me, I don't know why this happened. https://github.com/cloudflare/next-on-pages/issues/740
GitHub
next-on-pages environment related information System: Platform: darwin Arch: x64 Version: Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:27 PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 CPU: (16) x...
Bpages_build_output_dir.vercel/output
RYou need to set the “nodejs_compat” flag. In my tests, I had success when I configured the flag in the settings of the project on the dashboard.
RFor some reason the flag In wrangler.toml is ignored. However, In my case was a monorepo.
一Yes, it's already set.
一
Ttry to add the nodejs-compact to the wrangler pages deploy command and try to re deploy because If you manually add the nodejs-compact in the dashboard, you need to redeploy to see the effect
一GitHub
Contribute to hehehai/at4-kit development by creating an account on GitHub.
一I tried again many times
Ti saw you have prisma. this maybe not supported by next on pages
一Really? I'm using prisma and d1, so I'll switch to drizzle and give it a try.
一Do you know the specific reason why it is not supported? I see that the build and deployment was successful, but the deployed service failed.
Bprisma d1 is supported ofc
一Yes, I know it is possible. My local preview mode is normal. The problem is that the deployment results are not accessed in pages.
一it is like this
一Can someone try deploying this repository on pages to test it?
BIs DO rpc not supported for pages?
S^ Anyone familiar with using the suspense cache (basic fetch request caching, configured to use KV) to share data between build time (static pages) and server rendering time (pages defined with the edge runtime)?
JDo you have a reproduction you can share? I wasn't able to reproduce this with Next.js 14.0.4 or 14.1.4
JWe have no knowledge of what happens when Next.js builds your application, so I don't think it would really be possible for us to do that
J.vercel/output/staticHow can I interact with my production R2 buckets from next-on-pages? I need a way to upload an image and then get its public url
Nyou can't cache request at build time for ssr
Nand wdym by "static pages", its not possible to have both static pages and ssr on same project
SWe have that working fine right now, so yes, I'm pretty sure it's possible to have some of our routes render pages statically and some other routes be SSR!
The pages we built statically do not call the workers and simply serve what was rendered at build time, while pages using the edge runtime are SSRd just fine! (well, except for the issue I'm tackling right now regarding the sharing of data
)
The pages we built statically do not call the workers and simply serve what was rendered at build time, while pages using the edge runtime are SSRd just fine! (well, except for the issue I'm tackling right now regarding the sharing of data
)Jit is. only routes marked as edge runtime will be SSR. other routes will be prerendered at build time.
一We recently migrated our image hosting from Cloudinary to Cloudflare R2. This post details the reasons behind the switch, the pros and cons of Cloudflare R2, and how we implemented it in our codebase.
KHello! Is there any special configuration to run a fullstack application (with some pages on the server) on cloudflare? Everything is well installed, but when entering the web everything is black 
一Can you take a look at my problem? I saw that other people have encountered the same problem https://github.com/cloudflare/next-on-pages/issues/740
GitHub
next-on-pages environment related information System: Platform: darwin Arch: x64 Version: Darwin Kernel Version 23.1.0: Mon Oct 9 21:27:27 PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 CPU: (16) x...
Ji would recommend posting in pages-help or creating a support ticket. it will probably need an employee to check your deployment's logs to see if there is something going wrong there. it's possible your worker bundle might be too big for your plan (e.g. 1mb on workers/pages free)
Nare you sure ?
I get this error when not adding edge to routes
ERROR: Failed to produce a Cloudflare Pages build from the project.
12:27:51.712
12:27:51.712 The following routes were not configured to run with the Edge Runtime:
12:27:51.712
I get this error when not adding edge to routes
ERROR: Failed to produce a Cloudflare Pages build from the project.
12:27:51.712
12:27:51.712
The following routes were not configured to run with the Edge Runtime:12:27:51.712
- /ark-survival-ascended
12:27:51.712
12:27:51.713 Please make sure that all your non-static routes export the following edge runtime route segment config:
12:27:51.713 export const runtime = 'edge';
12:27:51.713
12:27:51.713 You can read more about the Edge Runtime on the Next.js documentation:
12:27:51.713 https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes
Learn about the switchable runtimes (Edge and Node.js) in Next.js.
Tyes. only edge route will have ssr, other route will be static prerendering at build time. you can check the static rendered page on .vercel output dir
S" Please make sure that all your non-static routes export the following edge runtime route segment config:"
^ The error is stating that you are trying to render a dynamic page statically, that's what isn't working
Please make sure that all your non-static routes export the following edge runtime route segment config:"^ The error is stating that you are trying to render a dynamic page statically, that's what isn't working
Nthat page is static
