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.
Support React-Redux v6.
See original GitHub issueReact-Redux v6 will use React’s ( new ) context api which is not compatible with the legacy context API. By accessing store from context ( reference ) it causes the app to break when it tries to dispatch the LOCATION_CHANGE action.
As @timdoor has described in its breaking changes:
Passing store as a prop to a connected component is no longer supported. Instead, you may pass a custom
context={MyContext}prop to both<Provider>and<ConnectedComponent>. You may also pass{context : MyContext}as an option to connect.
Related React-Redux links:
Issue Analytics
- State:
- Created 5 years ago
- Reactions:18
- Comments:14 (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
Based on @wgao19’s fix, I made a PoC in #191. Please check it out and let me know what you all think.
Update: I just published it as
connected-react-router@next(v6.0.0-beta.1).connected-react-router 6.0.0-beta.1 works for me with react-redux 6.0.0