Open exepowered opened 3 months ago
Facing the same issue here.
It seems that the problem is related to importing client components in the page.jsx
file.
same , the dynamic routes with export const runtime = "edge"
gives server side error in cloudflare pages
facing the same issue, any solution?
Personally, I switched back to Vercel, at least for now. They support Next.js natively, and apply some nice features e.g. image optimization that Cloudflare Pages doesn't support.
This is straight out of the docs but it doesn't work for me.
next-on-pages environment related information
Relevant Packages: @cloudflare/next-on-pages: 1.11.0 vercel: N/A next: 14.1.4
Description
I'm currently building a website with Next.js 14 and Prismic.io CMS. It seems like there's an issue with Dynamic Pages / Dynamic Routes on Cloudflare Pages deploy.
When deployed to Vercel or running locally, my app works flawlessly.
On Cloudflare Pages deploy, the pages are marked correctly as
λ (Dynamic) server-rendered on demand using Node.js
, but the deploy fails:When I add
export const runtime = 'edge'
to my failingpage.tsx
(although it should work under node.js default runtime, and it does so on Vercel), the page deploys succesfully asℇ (Edge Runtime) server-rendered on demand using the Edge Runtime
.Now trying to access the page, I'm getting this error:
Reproduction
Run a Next.js 14 (App Router) app with Dynamic Pages, and Prismic.io CMS in my case. Try deploying to Cloudflare Pages. Example code.:
Pages Deployment Method
Pages CI (GitHub/GitLab integration)
Pages Deployment ID
0a8c872 and 114366d
Additional Information
Found a similar issue here, but unable to fix: #32 and #35
Would you like to help?