Content pfp
Content
@
0 reply
0 recast
0 reaction

pugson pfp
pugson
@pugson
the inevitable curse of next.js + ORM cache is kicking my ass today. had to spend a few hours optimizing queries and rewriting to a client component to figure out some live piece of data πŸ˜΅β€πŸ’«
3 replies
0 recast
16 reactions

pugson pfp
pugson
@pugson
update: i am now back to a full server component and everything works perfectly lol
0 reply
0 recast
9 reactions

dylan pfp
dylan
@dylsteck.eth
they really need to change their caching defaults lol
2 replies
0 recast
1 reaction

Joe Blau 🎩 pfp
Joe Blau 🎩
@joeblau
Heh! I’ve run into this a lot… I had to throw 0 second cache limits everywhere to get next to give me live data. I probably should have just used web sockets.
0 reply
0 recast
0 reaction

CryptKid pfp
CryptKid
@kayzethegeek
I am a Frontend Developer and I have got expertise in Nextjs and Typescript, have you got opening for me?
0 reply
0 recast
0 reaction