Question 1

How do I fix 'Too many re-renders' errors with redux-react-hook?

Accepted Answer

This occurs when mapState isn't memoized. Wrap it in useCallback with correct dependencies to prevent new functions on each render, as explained in the README's troubleshooting section.

Question 2

Is redux-react-hook still useful after React Redux added hooks?

Accepted Answer

No, it's deprecated. Migrate to React Redux's useSelector and useDispatch for ongoing support, better performance, and ecosystem integration, as recommended in the project's deprecation notice.

Question 3

redux-react-hook vs React Redux hooks: which is better?

Accepted Answer

React Redux hooks are the official, maintained solution with top-down optimization. Use redux-react-hook only for legacy code; otherwise, switch to avoid deprecation risks and gain full Redux tooling.

Question 4

How to use reselect selectors with redux-react-hook?

Accepted Answer

Create selectors in useMemo for per-instance copies, then use them in useMappedState with useCallback, as shown in the README FAQ, to avoid resubscription and ensure proper memoization.

Question 5

Can I use multiple Redux stores with redux-react-hook?

Accepted Answer

Yes, via the create() function to generate isolated StoreContext and hooks, enabling management of multiple stores or type-safe contexts, though this is less common in typical apps.

Question 6

What are the performance implications of calling useMappedState multiple times?

Accepted Answer

Each call subscribes to the store, but re-renders are batched. For heavy usage, consolidate into fewer calls or return objects to reduce overhead, as noted in the README's performance tips.

redux-react-hook

What is redux-react-hook?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions