You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not yet sure how this would look, but it seems to be an issue. This was brought to my attention because of #9. The way this react-static-webpack-plugin currently works is by using the root <Route> as the root component, however, when using redux we need the Provider to be available or otherwise find some way of wrapping the rendered component in <Provider>.
Open to suggestions. The answer might be to rethink how react-static-webpack-plugin handles parsing and rendering routes to static files.
@scherler if you have any additional thoughts on this please let me know!
The text was updated successfully, but these errors were encountered:
I'm not yet sure how this would look, but it seems to be an issue. This was brought to my attention because of #9. The way this react-static-webpack-plugin currently works is by using the root
<Route>
as the root component, however, when using redux we need the Provider to be available or otherwise find some way of wrapping the rendered component in<Provider>
.Open to suggestions. The answer might be to rethink how react-static-webpack-plugin handles parsing and rendering routes to static files.
@scherler if you have any additional thoughts on this please let me know!
The text was updated successfully, but these errors were encountered: