The default flow/set-up from nextjs? or need to tweak some?
The default flow/set-up from nextjs? or need to tweak some?
KCloudflare Docs
If you need to run code before or after your Next.js application, create your own Worker entrypoint and forward requests to your Next.js application.
Jnextjs middleware runs on workers regardless of whether it's deployed to Vercel or cloudflare. Vercel use cloudflare workers for hosting nextjs middleware
PCan I use SSG (static site generation) on next-on-pages? I need that to create a blog. Not sure if SSR is good for that.
JIf you're using SSG you probably wouldn't need to use next-on-pages and could just do a fully static deployment instead
PThanks for answer. I would like to use SSG for /blog/* , but SSR for the rest 
Jah okay, in that case it will be fine as long as it's at build time
JDid you check out this page? https://developers.cloudflare.com/pages/framework-guides/nextjs/ssr/troubleshooting/
There are some other settings you might need to change due to how Nextjs generates dynamic routes
There are some other settings you might need to change due to how Nextjs generates dynamic routes
PThanks, added: export const dynamicParams = false . But same problem.
Kimport puppeteer from "@cloudflare/puppeteer";
can we use cloudeflare puppeteer inside nextj api route?
can we use cloudeflare puppeteer inside nextj api route?
Kor I'll just create a separate worker for it
PGo with separate worker 100%, you will have simple API to use it.
SHas anyone managed to get wildcard custom domains working with pages? I've tried using a proxy worker but I'm getting a 522 error. It works fine without the wildcard custom domain.
Se.g. *.example.com - mainly for SaaS stuff. https://developers.cloudflare.com/dns/manage-dns-records/reference/wildcard-dns-records/
SYeah, I need it to be wildcard for a SaaS product.
SYeah, they support it just not on pages for some reason. The workaround I've seen is to use a proxy worker (since you can use wildcard DNS there) but I get an error that makes little sense.
SYeah, I've seen that of course hence asking about the workaround or if anyone has got it working another way.
hence asking about the workaround or if anyone has got it working another way.Sa 522 error as above
SYeah, they're all pretty old which is why I figured I'd ask here
Sanyone know the answer to this? pages-helpHow can I access my d1 database in next on pages edge LOCALLY?
Jare you able to share some sort of repro by any chance?
Ndoes anyone know what could be the reason why a next/link in local dev mode doesn't cause a full page transition but deployed via next-on-pages it does?
Nweird it seems to transition fine when running with next dev but is doing the full page load if i try to run it with wrangler dev and the next-on-pages build output
JAre you able to share a reproduction?
NIs it possible that it's because the urls where it seems to full page load are " ● (SSG) prerendered as static HTML (uses getStaticProps)"?
I've noticed it seems to work fine on next on pages for the routes that are "ƒ (Dynamic) server-rendered on demand"
I've noticed it seems to work fine on next on pages for the routes that are "ƒ (Dynamic) server-rendered on demand"
Ni can send you the source via DM as it's not yet open source
DIt shouldn't matter afaik
BWhen using the
So, it’s hard to observe Next.js apps compiled with next-on-pages, and
Is there any plan to support
Related issues:
@vercel/otel library in a Next.js app that compiles with next-on-pages, then the CLI throws an error. So, we can’t use observability tools with OpenTelemetry (e.g., Sentry, Highlight.io). Furthermore, Cloudflare bought Baselime (observability tool) which supports OpenTelemetry standards, but we can’t use that either. So, it’s hard to observe Next.js apps compiled with next-on-pages, and
@vercel/otel not being supported is ongoing for 7 months. Is there any plan to support
@vercel/otel soon?Related issues:
SNextjs Middleware for App Dir
The middleware docs are not helpful for App Dir project. Not able to trigger the middleware. I even tried /functions/middleware.ts to no avail. How to go about it?
This is the closest thing I can find. Can someone confirm if this is the right way?
The middleware docs are not helpful for App Dir project. Not able to trigger the middleware. I even tried /functions/middleware.ts to no avail. How to go about it?
This is the closest thing I can find. Can someone confirm if this is the right way?
JYou can use default Next.js middleware
SI fixed it. The middleware.ts is supposed to be defined in the root dir and not inside of app dir. (which I was doing accidently)
Thanks anyway.
KHello 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 app directory:I 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.tsx file, only a layout.Will 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
