Fthis, i also have other pages using the same exact things, there's close to no difference which the structure of the website
FWhat do I do?
FI emptied the repo even more, all the components (except a theme switcher) are gone, and only the main page + an additional page (which starts breaking) is in here:
https://github.com/Headpat-Community/web/tree/main/src
(https://f36105b2.headpat-web.pages.dev/ for the latest commit with.. nothing in it)
https://github.com/Headpat-Community/web/tree/main/src
(https://f36105b2.headpat-web.pages.dev/ for the latest commit with.. nothing in it)
Flol
Jrunning this one locally with wrangler is giving me an exception so looks like there might be a legit problem with this one
Fbut what? i have the same structure on other sites, same files, same everything
FCould you remove the forgot-password folder and see if it works?
Jdowngrade to next@14.1.0
Ji downgraded and it worked
Fi linked to the /main/src, sorry haha
FWhen downgrading and using npm ci, it still says next.js 14.1.1, is there a specific command i need to run?
Jnpm add next@14.1.0
Foh that works, thanks! let me push and see
FThis seems to work on the test repo, will try on my main repo now
FYou're a life saver!
Thanks James.
Thanks James.
FAlthough 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
