Server-client hydration with Next.js

[cam-eo]

Is there a plan to cover Server-Client Hydration in RTK out of the box instead of using 3rd party packages like next-redux-wrapper which I see is actually mentioned here.

I'm just curious.

Because tools like TanStack Query cover this out of the box and works well but you end up needing an additional state manager for Client Side state management.

Considering the maturity of RTK I was just curious whether there is a plan to cover Server-Client hydration out the box without the need for next-redux-wrapper.

Looking forward to hearing any feedback.

[phryneas]

Why do you want to avoid that package? It's essentially impossible to use a Redux store with SSR without it.

[cam-eo]

Perhaps for SSR something like Tan Stack Query and a light Client Side State Manager like Jotai is a the way to go

@markerikson @phryneas thanks for the insights

[cam-eo]

We are like 3 people caring for all of this in our free time. Do you think we get paid for this? I personally get about 50$ a month in Github Sponsors, it's not different from the others.

How much more workload do you want to add because it makes sense to you that we do it, while there is already a person that also sacrifices their spare time to already maintain a perfectly viable tool for this exact purpose. That's not how Open Source works.

Wow I really didn't realize how limited resources are. The community is definitely in debt to you folks that work hard to maintain the package.

Knowing that resources are slim to none...totally understand.

[phryneas]

You will face the exact same problems with Jotai. SSR is an additional level of complexity. Nobody who maintains a state management library will have the stamina to support two dozen different SSR methods. If you are lucky you will find a third party library adding support for that.

To my knowledge nothing in TanStack Query is optimized for SSR with Next. It just gives you hints in the docs on how to create a new QueryClient for each Request. Essentially how to do the job that next-redux-wrapper does for you - but by hand.

Both of these tools are also maintained by 1-2 people, mostly next to normal work (Tanner is working on that stuff full-time, but on many more projects). Resources are so slim everywhere in the Open Source ecosystem.

[cam-eo]

Makes a lot of sense....I've been a bit disconnected from open source contribution world. Really makes me feel like I should contribute more.

When I mentioned Jotai, I mean only for Client Side state management for dynamic stuff like animations and Tanner only for SSR/Query stuff.

But I appreciate all the honesty🙏🏾

[phryneas]

No matter at which of your dependencies you look, you have a 90% chance it looks like this ;)

I can only recommend you don't get hung up on your distrust on projects like next-redux-wrapper. That will be a rabbit hole you don't want to get into ;)