Yeah I have absolutely no idea where that would come from, but it's probable that's something to do
Yeah I have absolutely no idea where that would come from, but it's probable that's something to do with how Next.js uses webpack(?)
JAh an early access thing, yeah, if anyone has an example it'll be the prisma team! Afraid that's not very helpful...
Mno problemo haha cheers for the help!
Myeah it's really irritating me as I'm pretty much stuck, I believe it's the fact I'm using clerk on the edge too but that seems to be compatible
JI recall clerk had issues early on with the edge but they worked with the vercel team to resolve those so i would be surprised if they were still problematic
Mmmm, gonna see if just hosting it on vercel somehow makes it work
Mscratch that, I can't get it to build locally now 
J
MI'm managing to get npm run build & turbo build working but I'm running into this issue again with the next-on-pages command pages-helpno such file or directory
Dsame here, wasm imports don't work with next-on-pages
https://github.com/cloudflare/next-on-pages/issues/676
https://github.com/cloudflare/next-on-pages/issues/676
GitHub
next-on-pages environment related information System: Platform: linux Arch: x64 Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023 CPU: (12) x64 AMD Ryzen 5 5500U with Radeon Graphics Memory: 3 GB Shell: ...
MAnyone know when this stuff could be fixed by? As it’s a blocker for me to launch on CF and the only other alternative is Vercel - which I don’t really want to use
Mlooks like a bunch of other people are also running into this issue btw, I'll list relevant GH issues/comments in pages-helpno such file or directory
WHey folks - trying to migrate from the previous
setupDevBindings to the new setupDevPlatform - I've got it working except it seems to not be pointing at the correct local sqlite DB for the D1 driver.
JHi @mr nooli @Deo Kumar, I've opened a PR that should fix this - please can you try this prerelease.
Vdoes nextjs app router and pages router apps run fine on pages? are there any limitations apart from image optimisations?
MYep 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
FHeyo!
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 :/
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 :/
Frunning npm run build locally works fine, but on cloudflare pages it takes about 5 minutes at least and then it just stops
MI 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!
MAn alternative - use GH to build your app and then push it to CF workers using wrangler, but it's a less elegant solution.
FThe 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 :/
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 :/
F
Whey folks- having trouble deploying my app to cloudflare. It seems only the static bits are being uploaded, I dont see any of the dynamic routes being turned into functions, or any of the bindings I've setup in settings show up. Should I be?
BI deleted my KV bindings since I switched to D1 but my builds are failing because somehow the builds still think they are there?
B
BMy build cache is cleared and disabled now
WAnyone have approaches for cron jobs with next-on-pages? I'd assume you can't use Cloudflare scheduled triggers within the same worker. Maybe another worker that pings our API endpoints?
WActually if I can add a scheduled handler to my worker, I could just re-implement the vercel.json cron with a switch case
WJust wanted to say thanks + fantastic job on the next-on-pages adaptor. I'm very impressed that all the cache + revalidate stuff "just works", and the development experience was really smooth.
J
FHey,
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:
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:
FThis is the log from the deployment
FOnly the pre-rendered routes work (however they only work partly and are extremely broken..)
FI don't know what to do about it :(
If something is wrong on my end, CF is giving me none of it, it's just ending the entire page sadly :/
If something is wrong on my end, CF is giving me none of it, it's just ending the entire page sadly :/
Lim trying to use ai with next on pages and im not sure where im going wrong. 
K
KCompressionStream isn't even a Node API, is it? It's a Web API which has been supported by browsers (and Workers) for years.
KThat's a weird error.
UDoes cloudflare ai really use the vercel ai package? 
UOr is this vercel being dumb and in the build of nextjs not allowing an api to be used at all
UI see
K
UGitHub
What's in there?
Middleware, since they are ran on edge runtime, do not have access to Node.js globals. While #36434 addressed cases where a middleware would import a node.js module, this PR is...
Middleware, since they are ran on edge runtime, do not have access to Node.js globals. While #36434 addressed cases where a middleware would import a node.js module, this PR is...
Ulol trying to file an issue on the nextjs repo is way too much effort
Lso that warning just needs to be disabled for next-on-pages, correct?
UI dont think next-on-pages can modify that at all needs to be fixed on the actual nextjs repo
Lno no i get that. what im asking is, this is supported when deployed correct? (if we get the error removed will it work?)
UOh I see, yes it would work when that is removed.
Lin that case i wonder if i can get around this for now with patch-package. 
