Persisting store state on page reload about next-redux-wrapper HOT 11 CLOSED

from next-redux-wrapper.

I’m rattling my brain with same issue right now. using a combination of state, session storage and cookies. Reconciling state is proving to be much more complicated, i either get true user object from a decoded token which is then unavailable on the client, or it’s available on the client and not on the server process. not a fun problem to solve

from next-redux-wrapper.

@rahulbhanushali @gpolyn you may use redux-persist. Here's the readme: https://github.com/kirill-konshin/next-redux-wrapper#usage-with-redux-persist.

from next-redux-wrapper.

I use this lib myself :)

The problem is that when you reload the page, then nasty collisions may occur if you hydrate it from two sources - server and client cache.

I have to think how this can be resolved.

from next-redux-wrapper.

If you use SSR then just store everything in user session there, I presume your rendering server and your API sever are not combined in one, so your API can still be stateless and renderer can have session/context. In this case everything will be done centralized and client will receive a full snapshot. Dump client state to renderer periodically to make sure it’s rendered correctly right away.

Or don’t use SSR if you’re dealing with RIA and not a traditional web site.

from next-redux-wrapper.

I also have this issue. i use express and express router with middlewares for routing and authentication, but everytime i switch to another page the redux store falls back to its initial state. i also tried to hook it up with redux-persist, but that didn't workout.

when i use it with next-routes or the built in routing system the store keeps its state. do you have any examples on how to make this behaviour happen when managing the routes with express?

from next-redux-wrapper.

Closing since there's nothing much to do in scope of the library. Any PRs are welcome, I will reopen if there will be any.

from next-redux-wrapper.

@kirill-konshin in practice, with production redux apps do users refresh the browser or manually enter an app URL and lose state?

I can't tell from discussion of this topic (elsewhere) whether this is something users of redux, next-redux-wrapper should design for.

from next-redux-wrapper.

I am still facing the same issue, where I lose the state in my redux store on page refresh.
Anybody solved this using local storage? Don't want to use cookies here.

from next-redux-wrapper.

Thank you this worked well.

from next-redux-wrapper.

@kirill-konshin https://github.com/kirill-konshin/next-redux-wrapper#usage-with-redux-persist . ssr does not work in this instance, if you try to check the HTML markup, then it is not. But localstorage works, I haven't found a single instance in which ssr, localstorage, redux, redux-saga works. help set up ssr instance, localstorage, redux, redux-saga, wrapper.

from next-redux-wrapper.