Video yükleniyor...
Video Yüklenemedi
"How to share state between React client components with a parent server component?" 👇
50,550 görüntüleme • 1 yıl önce •via X (Twitter)
9 Yorum

Although it’s quite obvious, you did not add count-provider code

is there a reason for using `use` instead of `useContext`?

nope, same result

This vs. Zustand what is your take?

Depends on the type of the app. If it's an interaction-heavy app with a lot of state sharing -> client state lib, if not, context provider here and there is fine

This looks obvious, but what about sharing state between server and client components? I’m using queryparams, not ideal tbh

Why not ideal?

wouldn't it be better to zustand in each client component and thus avoid adding code in the server component? or is it just the demo with contextApi?

if the context is defined server side, doesn’t this imply the single context is shared across all users visiting the web app? as I understand if I define a zustand datastore, wrap it in a provider, mount it on a server component, all users will share the same store
Benzer Videolar
How to recover from a server component error in Next.js
Alex Sidorenko
67,557 görüntüleme • 1 yıl önce
Moving data fetching between client and server with SWR
Alex Sidorenko
33,430 görüntüleme • 1 yıl önce

