Hello does zustand works well with next-on-pages?
Hello does zustand works well with next-on-pages?
PYep, I use it for my project, and I have no issue with it.
AI was using WARP DNS VPN(1.1.1.1) for ONLINE servers. I can't get in with it anymore. I asked Server FOUNDER. Cloudflare said it blocked it.
I wonder why it was blocked?
I wonder why it was blocked?
Bhi fellow next people, how do you do logging/error tracing on next-on-pages ? what is the recommended way? im tired of constantly having to tail the deployment in order to see any significant logs
MHello, I think you might be able to help with this issue, and I appreciate your assistance in advance.
I am developing an application with Next.js, which I deployed successfully to Cloudflare Pages and connected to my domain. Afterward, I set up a proxy using a Cloudflare Worker. I am using the next-intl library. The language changes do not reflect on the components in the pages, but everything works correctly when running locally in dev mode with Wrangler or after building the app. SEO content is rendered correctly in the appropriate language in these cases. All caches are disabled. Since everything works locally, I cannot pinpoint the source of the issue.
When I run the Worker locally, I can see that all requests and parameters are correctly sent from the client to the Worker. I suspect that Cloudflare Pages is not correctly handling my Next.js application and is continuously serving the default language preferences. I can also see the language change in the cookies. Can you help me with this?
I am developing an application with Next.js, which I deployed successfully to Cloudflare Pages and connected to my domain. Afterward, I set up a proxy using a Cloudflare Worker. I am using the next-intl library. The language changes do not reflect on the components in the pages, but everything works correctly when running locally in dev mode with Wrangler or after building the app. SEO content is rendered correctly in the appropriate language in these cases. All caches are disabled. Since everything works locally, I cannot pinpoint the source of the issue.
When I run the Worker locally, I can see that all requests and parameters are correctly sent from the client to the Worker. I suspect that Cloudflare Pages is not correctly handling my Next.js application and is continuously serving the default language preferences. I can also see the language change in the cookies. Can you help me with this?
M
Bcan you clear the caches just in case?
MYes, the cache has been cleared. In fact, it has been completely disabled.
MAt the endpoint, also disable the proxy and use DNS only.
JWhen you run wrangler pages dev does it work properly?
MSince wrangler dev was working correctly, but errors occurred on Pages, I focused entirely on investigating Pages for a while. I discovered that the error was caused by an environment variable I had set on Pages, which had actually been changed but was still active on the backend, leading to incorrect results. Now, everything is working smoothly without any errors, and it's working really well. Thank you (=. 
JAh nice, glad to hear
LHi people, how are you? I'm trying to use Firebase Auth with Next Auth, that is, the Firebase login is executed in a Next Route, all deployed, but when I deploy and try to use it, it doesn't work. I see the logs with the following error:
EIs anyone else getting this error?
This is the contents of my
I also have a
Versions:
Build command is:
I've tried building after deleting both
I've also deleted the
I've also tried downgrading nextjs to version
I've went through every
Happens on both my windows machine, and on pages when building on cloudflare
This is the contents of my
error.tsx at the root of my appI also have a
not-found.tsx with this:Versions:
Build command is:
"pages:build": "npx @cloudflare/next-on-pages",I've tried building after deleting both
error.tsx and not-found.tsx and the error persists.I've also deleted the
.next, .vercel, and node_modulesI've also tried downgrading nextjs to version
14.0.0 as I saw that's what was used in the next-on-pages e2e tests, and the issue persists.I've went through every
.page.tsx, layout.tsx, and route.tsx, and specified the edge runtime, I'm completely stumped.Happens on both my windows machine, and on pages when building on cloudflare
TTry removing that 'use client', also remove 'async' from the NotFound() function, and finally make sure you are not computing stuff inside not-found.tsx
ERemoving
Tried taking out the
use client from error.tsx gives this:Tried taking out the
asyncnot-found.tsx (which doesn't have any logic, just returns a div saying "not found", and it still gives the same error:EIf anyone searches this, managed to get it working.
My root
Which for my use case was fine, nearly every page retrieves data from a CMS, not much gets statically rendered.
Deleting the root layout fixed it and it built successfully, I wonder if it's because I'm using the
Will look into it more tomorrow but at least I've found how to make it compile!
My root
layout.tsx file had the following:Which for my use case was fine, nearly every page retrieves data from a CMS, not much gets statically rendered.
Deleting the root layout fixed it and it built successfully, I wonder if it's because I'm using the
platforms approach, so don't have a root page.tsxWill look into it more tomorrow but at least I've found how to make it compile!
LHey everyone, I have the same issue. In my root file, layout.tsx, I added the following lines of code:
export const runtime = 'edge';
export const dynamic = 'force-dynamic';
export const revalidate = 0;
export const runtime = 'edge';
export const dynamic = 'force-dynamic';
export const revalidate = 0;
DI think the problem is that the edge runtime doesn't have http and https modules so you should use the built-in fetch
L@D Trombett But in the Vercel deployment, it runs perfectly without these lines:
export const runtime = 'edge';
export const dynamic = 'force-dynamic';
export const revalidate = 0;
export const runtime = 'edge';
export const dynamic = 'force-dynamic';
export const revalidate = 0;
Lif any solution for this please give me
DBecause Cloudflare next-on-pages requires edge runtime at the moment
DWhile vercel doesn't
Acloudflare pages is basically useless for next.js app with runtime = 'edge'. Hope they introduce improvement related to this in birthday week
�What does the runtime edge limit in functionalities ?
Aso many, can't use firebase-admin sdk, mongodb sdk etc...
�Oh that interesting ahah, because i want to make a next app using supabase so i imagine that i will have some problem to host it on pages ^^'
AI'm using google cloud run atm, will switch to pages once they fix this. On workers with new node_compat_v2, we can use mongodb sdk I guess, though I've not tried it.
�I will finish by hosting it on my own kube cluster...
Acheck this: https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/supported-features/#nodejs
Cloudflare Docs
@cloudflare/next-on-pages supports all minor and patch version of Next.js 13 and 14. We regularly run manual and automated tests to ensure compatibility.
�Mmhhh, i have some people who are hosting on pages their app with supabase on reddit. But by reading on this feed it look like also some people facing some issue using pages and supabase
JThis is a next.js build error and not something we have control over
Ti dont have error in code :{
Twhat is wrong with it
IYou have ESLint enabled and set to error when it finds a lint that's not followed.
IEither fix the issue (don't use
any
�It was also that he didn't have installed next on pages module. (He asked help in dm and i have help him)
THow can I find what is causing high TTFB in next-on-pages project? Mine has been around 1.7s for the last week so and it hurts me so much
In an example page, I do a KV fetch (probably cached) and render stuff that's all
In an example page, I do a KV fetch (probably cached) and render stuff that's all
FCurious if cloudflare would support partial pre rendering one day 
I think Vercel uses node for it but I guess could also be done with edge ?
I think Vercel uses node for it but I guess could also be done with edge ?JThat would depend on Vercel not requiring it uses Node.js-based functions for next-on-pages.
PSuch a lol, fast refresh doesn't work when running
npm run devnpm run preview doesn't work within powershell as wrangler does not want to work. Switching between the two is GREAT fun.
KHello has anyone got this error
"message": [
"error code: 1016"
],
it says Cloudflare is unable to send requests to a server, I got it on my preview branch but on main branch its working fine
"message": [
"error code: 1016"
],
it says Cloudflare is unable to send requests to a server, I got it on my preview branch but on main branch its working fine
Kthe request is in the server component in nextjs, when I change the base_url to my production url it works fine
DIs there a way you guys could add more node options within settings presets? also bump bun to 1.1.20+
Dit's currently using 1.0.1 which is quite old, probably more than a year old
TNeed some help to understand this issue.
So I started my next.js project with the pre-configured script
Using radix-theme for the UI, but during build I get
Any help to resolve this issue will be highly appreciated
So I started my next.js project with the pre-configured script
Using radix-theme for the UI, but during build I get
Any help to resolve this issue will be highly appreciated
Jyou can set
BUN_VERSION env var to override the bun version
Ji would recommend opening an issue in radix since it seems to come from there
OI suppose this is happening when you try to change your layout/page's runtime to edge? If so then just create a page.client.tsx file and export every single component from that file using
'use client' after that do all the server stuff in page.tsx and it should workDcool, how about node version?
