A place for developers to talk about building on Farcaster.

/dev

DX Engineer | Head of Developer Relations at /pinata | Building orbiter.host | stevedylan.dev/links | opinions are my own

share more pls, was next applying its fetch cache settings on node-fetch?

Lowkey thinking about doing a write up on this whole escapade. It’s so absurd I think more people need to be aware how deep Next.js goes. 

I need to retest the scenario on v15 instead of v14 which a client was using and took us days to debug.

It's ROUGH. Definitely one of the things @polluterofminds and I are fighting with Orbiter, e.g. Andromeda.build 

Personally love using simple Vite + React for mini apps. Check out the barebones template here:

It's ROUGH. Definitely one of the things @polluterofminds and I are fighting with Orbiter, e.g. Andromeda.build 

Personally love using simple Vite + React for mini apps. Check out the barebones template here: https://github.com/orbiterhost/orbiter-templates/tree/main/templates/mini-apps/react

I started the mini app I just published a few days ago being like oh I should look into what all the cool kids are doing for routing and whatever else and it ended up just being boilerplate hell of some router bs ssr requiring like 50 LOC just to make the embed frame json object work if I didn't want to hardcode it in the index.html I very very nearly swapped straight to a single page sveltekit project but just went to the official create mini app one. The complexity these days is crazy

😅. Actually, yes they were patching next in v13 and I think early 14. But people complained then the stopped. But I wouldn't be surprised there's still isssues. There's always something weird in Nextjs

@blockbot Steward. Frames Builder. Pro Chess-er ♟️


Turns out it was patched in v15 so glad to see that 😮‍💨 

Basically they were applying cache settings to node-fetch inside SDKs and from what we could tell there was no way for a user to override it. If they wanted to use v14 with our SDK and prevent caching content we would have to make a patch to our fetch requests inside the SDK to use cache: "no-store" (which we did just to be safe). What's even more insane is that these are POST requests. It makes zero sense to cache a post request like that 🫠

Bringing tech into Crypto(Web3).

#Marketer #Web Dev #DataAnalyst #Crypto

Just some days ago I was looking for error on _not-found.tsx that wasn't even on my codebase at all, crested a not-found file to overwrite it but still the same error.

Until I have to re rewrite everything and found out it was due to the Authkit I was using.

oh shiz that's me 🫨

re NextJS, it's the only thing that made me feel both very stupid and smart once I learned all its hidden behaviors and knew it like an extension of myself

What are some of the main reasons you use Next.js? Genuinely curious