Hi @mr nooli @Fineshop Design, I've opened a PR that should fix this - please can you try this [prer
Hi @mr nooli @Fineshop Design, I've opened a PR that should fix this - please can you try this prerelease.
16 Replies
does nextjs app router and pages router apps run fine on pages? are there any limitations apart from image optimisations?
Yep absolutely does! I was for a short time running https://cruncho.app on there but the app got too big that pages stopped being able to build it :/ which meant I had to unfortunately switch back to Vercel
Heyo!
I am suddenly getting "build exceeded memory limit", but the only thing I did was change from client pages using route handlers to server-sided api calls, is there something going on? I am unsure why this is suddenly happening :/
running npm run build locally works fine, but on cloudflare pages it takes about 5 minutes at least and then it just stops
I had this issue too a while back with Cruncho, didn't dig into it too much, just figured that there wasn't another option than to switch away, but hopefully someone will be able to help you out!
An alternative - use GH to build your app and then push it to CF workers using wrangler, but it's a less elegant solution.
The issue with using wrangler, it's for static content
As I am using non-static content as well, it's not for me. But as said it worked fine for me but suddenly it's taking like 6 minutes just to build (instead of 3 for example, and after 5:45-6 minutes, it just says this, super disappointing and would love to know why this is happening :/
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
I deleted my KV bindings since I switched to D1 but my builds are failing because somehow the builds still think they are there?
My build cache is cleared and disabled now
Unknown User•9mo ago
Message Not Public
Sign In & Join Server To View
❤️
Hey,
I published a version of nextjs on a cloudflare page using git integration, but it's failing miserably.
I would like some help ASAP if possible, the page build succeeds, but nothing of the page itself makes sense.
Routes are missing, the front page (static) shows a 404, the real-time logs show this:
This is the log from the deployment
Only the pre-rendered routes work (however they only work partly and are extremely broken..)
