Although I wonder why 1.4.1.1 is causing this many issues on CF? It's not like that much has changed
Although I wonder why 1.4.1.1 is causing this many issues on CF? It's not like that much has changed
Jit looks like a bug they introduced in 14.0.2 and refuse to fix or accept my PR in nextjs to fix, but our regex hack for it isn't matching in your build
Fahh I see
FWell, thanks for the help! 
Jno worries
JI think something about the minification they do has changed
FThanks!
Lis there a way to use bindings with server actions? i want to have my server action send a request to cloudflare ai but when using the get request context i get an error. 
Lfound the answer: you need to make sure that you set the page.tsx as edge if it's using a server action that needs the cloudflare env.
https://github.com/cloudflare/next-on-pages/issues/680#issuecomment-1965641204
https://github.com/cloudflare/next-on-pages/issues/680#issuecomment-1965641204
GitHub
next-on-pages environment related information System: Platform: linux Arch: x64 Version: #17-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 11 14:01:59 UTC 2024 CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-1362...
LIs there any way to see live logs? The docs suggest you can for workers but i cant find that for next-on-pages.
Hhttps://dash.cloudflare.com/?to=/:account/pages/view/:pages-project/:pages-deployment/functions, then scroll down to Live Logs
Ldoesnt exist?
Lif i do a ctrl+f i see only the sidebar showing logs nothing else on the page.
HHave you selected your Pages project?
Lyep, and for other users on twitter they all had a logs tab here. i also dont have that.
HClick one one of the deployments shown.
Lthat gives me deployment logs..? still not seeing live logs at all.
if i switch to a normal worker the logs tab exists.
if i switch to a normal worker the logs tab exists.
HDoes your URL look something like this? https://dash.cloudflare.com/864cdf76f8254fb5539425299984d766/pages/view/wdol/208d2146-67f5-4468-9793-3d69b0461e0d/functions
Lomg why is it soooo buried. 
thank you thank you.
thank you thank you.
HI think the deep-linker is broken lol. Going to report it
Lideally id be nice to have that as a tab like the normal workers do. kinda weird them being different yet within the same area.
HI think the reasoning there is that your logs are tied to a specific deployment, so if anything, once Workers get deployments, they will do it the same way
Lwould still be nice to have them in that top tab even if it somehow filtered them. currently it feels like i need to hunt for the logs. 
UIt would be in the browser console as the error says
BEnable real time logs
Bgo to the deployment and then functions and then real time logs
B
Bthen click begin log stream and do the action again that caused the error
BNot really familiar with github actions and cloudflare, so couldn't help you there
KJust means that you exceeded either CPU runtime or memory
KYou'd have to look at the tail logs to figure out which it was
DDoes anyone know how can we catch all https methods in next js api routing?
JDon't think Next.js supports doing that
NHey - what’s the general experience with Next on Pages like these days? We have a fairly large site on AWS amplify and looking to move to something that is cheaper and supports streaming. Lack of NodeJS APIs is no issue because we don’t use any
Ucompared with amplify it would probably be about the same 
NWhat are gotchas? Does it support actions and App dir well?
UIt should yes
ZI'm trying to migrate ecommerce site from next on aws to CF pages and I'm having: 22:28:12.755 Failed: build exceeded memory limit and was terminated
Zfound some threads where CF team was opting out people from instrastructure upgrade in situations like that and it helped, could we try that?
ZMy current goal is to do PoC if core functionality of our next page could work on CF, then we could start tweaking and playing with it more
IDoing this migration right now - so far so good. We could never work around the cold starts issue on Amplify and what we have moved is lightning quick on Pages.
JYou could maybe try building it in git actions and deploying with wrangler instead?
Zyou mean some specific gh action?
