0

I'm in the process of updating all of our npm packages for our frontend codebase, which has been locked at years old versions because of some updates requiring major changes in the code.

Some of these packages revolve around redux and react-redux. After updating to the latest versions, some deeply nested components can no longer identify the context being passed down from the main component, which is wrapped in a <Provider store={store}>.
I feel like I've tried everything in my toolbelt by now, and I'm kind of at my wit's end.

TL;DR - After package updates, deep nested components no longer recognise passed down context from main component wrapped in provider.

Does anybody have any insight on this sort of problem?

Comments
Add Comment