devFC

Farcaster Builders International

NextJS Server actions maybe what screws you here

That’s NextJs related and not a mini app / neynar bug

I‘d search NextJS docs here to figure it out. Since we don’t use NextJS server actions and only advise NextJS usage if you host on vercel I sadly don’t have much more input here without trying to debug your code directly besides untangle server actions into traditional Frontend -> backend calls

NextJS outside of Vercel is an anti pattern.

Server Actions in general are too.

NextJS can be good tech, but doesn't make you use it as good tech by default. 

Constraints are good. Make it hard to do the bad things >>> make everything easy. NextJS tries making everything easy and therefore makes shit hard if you aren't on the happy path.

That's why some of you may have noticed I am not the biggest next fan. It's not Next. It's how next usually is used.

And yes we run production apps on Next on vercel. 

We don't otuside of Vercel though. Anything outside Vercel you'll almost never see me advocate for NextJS.

Tried that e.g. with Frames. Post Routes went from 200ms response times on vercel to 2s response times and yes I was geographically very very close to the VPS running the NextJS instance and it had 16 cores, 64GB ram so definitely not network & hardware limited!

to be honest, i heard first time about this issue. what version of nextjs do you use in your projects?

i found almost the same thread as you described on the github:
https://github.com/vercel/next.js/discussions/58676?utm_source=chatgpt.com

maybe that is the case?

Farcaster Development Boutique @ https://dTech.vision 💜 in love with tech 🤓decentralization, fitness and oldschool rap 😎

your favorite software dev • crypto degen • miniapps lover • full time warpcast caster

i also checked some analytics, and those times can be worse, but about 30%, not 1000%. definitely something wrong except the hosting service

would need to go back and double check version etc.