Meaning of the hydrating flag in the new version about next-redux-wrapper HOT 3 CLOSED

As someone migrating from 8 to 9, I encountered the same problem as you but just got it to work.

There were a few of gotchas in the readme that I miss due to not being observant:

In your makeStore (the first argument you pass into createWrapper), you now need to expect an object containing the property reduxWrapperMiddleware. e.g. const makeStore = ({ reduxWrapperMiddleware }) => {}.

Plug this into the end of your middleware list.

For redux, it's

const store = createStore(rootReducer, applyMiddleware(sagaMiddleware, reduxWrapperMiddleware));

For redux-toolkit, it's

const store = configureStore({
    reducer: rootReducer,
    middleware: (getDefaultMiddleware) =>
      getDefaultMiddleware().concat(sagaMiddleware, reduxWrapperMiddleware)
  });

For the props object you pass into useHydration, make sure it has one of these properties: reduxWrapperActionsGSSP, reduxWrapperActionsGSP, reduxWrapperActionsGIAP or reduxWrapperActionsGIPP, depending on what lifecycle method you use (e.g. GSSP = getServerSideProps).

If they're missing, then likely your component is not receiving the correct props. Your component should receive props.pageProps from your _app.js.

Those properties should also not be an empty array, they should contain a list of actions to dispatch to hydrate your store.

from next-redux-wrapper.

Hi, thanks for the reply and sorry for getting back to you so late.

I have indeed implemented all of this exactly the way you described and the problem still persists. However I've encountered a different problem which may be the underlying cause of this one, but since it causes other problems as well I think it merits another issue, I'll link it here when I post it :).

from next-redux-wrapper.

The issue was me calling useHydration multiple times, since I have custom _app it is actually enough to just call it there :)

from next-redux-wrapper.