Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
autoRehydrate does not lift the reducer it makes
See original GitHub issueFinally found the root cause…
Problem:
if you use redux-devtools & call replaceReducer, the initial state overrides the persisted state.
Reason:
replaceReducer doesn’t know about the reducerEnhancer that autoRehydrate() creates. That means the devtools inits without it, and doesn’t merge the initial state with the persisted state.
Reproduction:
Call store.replaceReducer on an async route. (Probably works on sync routes, too. Haven’t tried).
Workarounds: None (use redux-storage?)
Fix:
Either offer a reducerEnhancer like redux-storage or lift the replaceReducer into the liftedStore. I think the former is cleaner because autoRehydrate does not need a lifted store, so using a higher-level API seems reasonable.
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
the latest version now lifts the reducer. I am using it in a HMR environment and it works. If there are outstanding issues please reopen!
@mattkrick thanks for the reference now i understand what you mean by lifted reducer 😃
I believe we can classify this as a bug, and fix by lifting the reducer in v3. For v4 I will reconsider the higher order reducer option.
redux-storage is a great choice as well, I am glad that worked out. Redux persist does a lot to be performant out of the box, hopefully after we get all of this sorted you can give it another try 👍