next-auth-sanity VS next-redux-wrapper

In the middle of development this sanity plug-in was released for storing auth data in sanity: https://github.com/Fedeya/next-auth-sanity

RTK Query uses another library (next-redux-wrapper) to wrap getServerSideProps and allow the usage of redux server-side.

Next.js documentation on data fetching and state Next.js documentation on server components Redux documentation Next.js Redux Wrapper documentation

That's how you can integrate Redux with a Next application! You can find the GitHub repository for this project here. I would also encourage you to review the documentation of next-redux-wrapper to learn more about other use cases.

I’d suggest reviewing the docs for the repo and see if their use cases for yours.

This library comes up again and again: https://github.com/kirill-konshin/next-redux-wrapper

I try to follow the tutorial which shown on the next-redux-wrapper but no success. Nothing change.

That's why there's a fairly complex library called https://github.com/kirill-konshin/next-redux-wrapper , which tries to abstract the process of grabbing data from the server-side APIs and rehydrating that data into the Redux store on the client side.

I just hopped on this project that uses nextJS, and since most of the guys working on it were mobile devs first, we are using this library to use redux sagas.

Hi! I have never used Redux with Next.js before. I've searched for tutorials - some ignore the SSR entirely, some use something called "redux-toolkit", some use something called "redux-wrapper". All of this is confusing and overwhelming, and I don't know enough to figure out which approach is the correct one.