Heyo o/ Did you manage to solve this and if so how?
Heyo o/
Did you manage to solve this and if so how?
Did you manage to solve this and if so how?
DI'm also getting 405 Method Not Allowed with the NextJS actions
FI haven't fixed it. I migrated away from Next.js on Cloudflare Pages ):
Fi'd gladly migrate back if that issue didn't exist tho
DI have found a work around but now I'm getting this every time I submit the form
Fwhat's the workaround?
DI tried this in different files until it worked 
DIn my case I have it on page.tsx
DWhich has the component with 'use client' with the form
MHi, how can I know the exact file that cause this error?
MI just re-run any successful deployment in the past, and the error is still there, maybe it's not the nextjs's problem
DIf you could move to the paid plan the limit there increases to 10MiB: https://developers.cloudflare.com/workers/platform/limits/#worker-size
OHi guys, i'm unable to make Cloudflare next-on-pages work on development using Docker. When i run the app locally it work well, but when i run the same app on Docker environment it just crash.
Github repo for reproduction. https://github.com/oljimenez/cloudflare-app
Github repo for reproduction. https://github.com/oljimenez/cloudflare-app
GitHub
Contribute to oljimenez/cloudflare-app development by creating an account on GitHub.
ZI'm working on testing migrating next project to cf pages, seeing some issues here and there I wonder if anyone launched productionally some more complex site, not just static pages (like ecommerce frontend)?
Thow do I get support with image optimization for cloudflare pages use next-on-pages in nextjs
Thow do i set up the prisma with next-on-pages applicataion?
NIs anybody knows how to access Cloudflare Environments (KV, Workers AI etc) in server actions?
BGitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
BGitHub
CLI to build and develop Next.js apps for Cloudflare Pages - cloudflare/next-on-pages
DFor image optimisation on edge runtime, you can use https://github.com/node-libraries/wasm-image-optimization
GitHub
Optimize images with wasm on edge runtime. Contribute to node-libraries/wasm-image-optimization development by creating an account on GitHub.
CI've been unable to use Server Actions with next apps deployed on Cloudflare Pages. The only working solution is the one in this comment (https://community.cloudflare.com/t/next-js-server-action-error-405/601134/3), which is to set the
If I have a simple page with a form that has a Server Action, and I set the runtime to
runtime = edge, but that nullifies static generation, right?If I have a simple page with a form that has a Server Action, and I set the runtime to
edgeIn my experience this also introduces other weird issues throughout the app that are hard to debug the more complex it gets.
CBasically for me, if you're saying Server Actions are compatible with Cloudflare but you have to do this to your project that's very misleading. I hope I'm missing something, new to the overall Cloudflare infrastructure offering so I don't know the nitty gritty details.
CIs there a way to keep a page statically generated, while using Server Actions? Or will that never happen on Cloudflare, it's either full static or full dynamic?
HAs I understand, it is a limitation of Next itself. It's server expects control over serving all pages/assets, so all routes will incur functions requests, regardless of whether or not they are actually dynamic
CAlright, so if I have a page that doesn't need hydration, doesn't have any interactive stuff, not even server actions (so not setting
runtime: edge), will that page be statically generated and served like it would be from R2/CDN basically? Or is everything run each time, even the 100% static pages. I'm trying to figure out how the NextJS bundle generation, NextJS caching, Cloudflare caching, and overall Cloudflare infra work together. Are there any resources about this I can read?
JIf you're using @clourflare/next-on-pages, you will incur a function invocation for every request. Your pages may be prerendered at build time and these pretended files will be served instead of doing SSR, but it still results in an invocation because requests to routes need to go through the routing system so that they can correctly match up with the right prerendered file or edge function, based on rules determined by Vercel during build.
JI haven't actually investigated the 405 with server actions before, but if you're calling it from a prerendered route, i would speculate that on Vercel they bypass the prerendered route and invoke the nodejs function for action calls on static routes, which is not something we are able to do. Again, I haven't looked into it before, but that would be an initial assumption.
CAlright, but to clarify, the message in the console at build time (whether it's in a next-on-pages or plain create-next-app) that says "enabling edge runtime disables static generation" is correct, right? The request that Cloudflare will make will be one to render the page each time, not to get it from a file bucket with pre-rendered pages (even if the page has no interactivity, but it has the
edgeThanks for the help James!
JYes, if you enable the edge runtime for a route, it will always create an edge function, because Vercel don't want to support prerendered routes or ISR when someone uses the edge runtime.
When the edge runtime is enabled, it creates a function that is run at each request to SSR the route.
When not using the edge runtime for a route, it will be prerendered and served from the static assets by the router.
When the edge runtime is enabled, it creates a function that is run at each request to SSR the route.
When not using the edge runtime for a route, it will be prerendered and served from the static assets by the router.
CYou're a boss, thanks!
PHi, I have a turborepo including a Next project that is deployed on CF pages. Everything works fine, but build caching says 'Skipping build output cache as it's not supported for your project'. Is this due to using turborepo? The source directory to build in is set to the app directory. Or why would the build ouput be skipped?
PAlso yarn v3 dependencies located in .yarn/cache are not being cached, I wanted to set the yarn cache dir to .next/cache/yarn to make it work, but due to the build output cache being skipped, that workaround is not possible.
Many luck with this? I'm getting this trying to run prisma & the neon driver
MI believe potentially due to using a singleton pattern for the prisma connection, is there an example I can look at on how to use neon & prisma in a CF worker
CThe right way of using prisma is by installing drizzle (https://orm.drizzle.team/docs/get-started-postgresql#usage-with-cloudflare-workers)
Drizzle ORM is a lightweight and performant TypeScript ORM with developer experience in mind.
PHello! I’m about to try this, but does this setup https://developers.cloudflare.com/pages/framework-guides/nextjs/deploy-a-nextjs-site/ allows next ssr functionality? In other words, is this can replace Vercel completely? Thank you
Cloudflare Docs
Deploy a full-stack Next.js site (recommended).
JYes you can have SSR if you opt a route into the edge runtime
MI am trying to deploy nextjs 12 on CF. but said to add edge runtime to SSG or ISR pages like first image. I export the edge runtime as like 2nd pic but after that CF says that same error. The last image is the build config. How can I solve the error?
Mand my nextjs version is 12.1.0
PHas anyone got Sentry logging (server + client) up and running with Next on Pages using the App router?
PDoesnt seem to work if I follow the sentry install wizard of their next plugin
PI also have another issue with next-on-pages where sometimes the revalidateTag in a server action is returning the error: "Error: Invariant: static generation store missing in revalidateTag X"
Ti have a question: is there any tool that can convert the code nextjs written in nodejs to cloudflare edge runtime (v8 engine) to deploy in cloudflare
JNot currently
I
Also curious about this, I wanna try out vercel's open telemetry package soon, for workers people use generally ToucanJs, a sentry compatible package, but it hasn't been updated in a while. I know a while ago there was some conversation in the sentry cliënt GitHub. Keep me posted if you find a nice solution, I'll look into this in the next coming weeks too!
PTry placing it at the very beginning of the file
PDoes —turbo flag apply for cloudflare next-on-pages ??
PAnother question, are the server actions functional with next-on-pages ? https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations
Learn how to handle form submissions and data mutations with Next.js.
