is the store a fresh store in each client side route change? about next-redux-wrapper

[kirill-konshin]

The store is singleton an is preserved during client side navigation. If you reload the page then store will be created from scratch.

[pratheekhegde]

But when getServerSideProps is used, during client routing the state is being replaced by what getServerSideProps returns. __NEXT_REDUX_WRAPPER_HYDRATE__ is called every-time when client routing happens.

[kirill-konshin]

@pratheekhegde it depends how
You handle the action in reducer. You should cherry-pick things from hydrate action’s payload instead of replacing client state completely.

[pratheekhegde]

@kirill-konshin Thanks for responding. But how can we identify if it was a direct SSR load or client side navigation?

[kirill-konshin]

@pratheekhegde https://github.com/kirill-konshin/next-redux-wrapper/blob/master/README.md#server-and-client-state-separation

[pratheekhegde]

@kirill-konshin I have read the link and I understand the strategy. Apparently, I'm trying to port an existing react-native-web app to next and it would take a considerable amount of effort to separate the exiting store to client and server.

But how can we identify if it was a direct SSR load or client side navigation?

Is there any way to figure 👆🏻 out?

[kirill-konshin]

@pratheekhegde you can have some boolean in the state and set it to true on server and in HYDRATE handler do things appropriately. It is up to your application logic to figure this out.