recompose VS fluxible

Maybe take a look at the recompose project. https://github.com/acdlite/recompose https://medium.zenika.com/react-hooks-my-introduction-81b15e6eff20

A lot of stuff from functional programming are used in react. Hooks were basically recompose: https://github.com/acdlite/recompose

For those curious this is the result of using recompose

I am using recompose in my React projecthttps://github.com/acdlite/recompose/

Should I dispatch a separate action like SELECT_LIST_ITEM in componentWillReceiveProps e.g (using recompose):

Along with classes you'll also gonna need to learn how people achieved composition before hooks. Namely higher order components. You may also want to checkout js library https://github.com/acdlite/recompose which was often used in tandem with higher order components.

And in the end, you will need to compose your app with all that HOCs. For that, I like to use the Recompose library. It has other powerful uses, but for now we will use only the compose.

Using libraries like recompose

I might look like an asshole, but that also can save you time on future work: recompose includes withState and many other HOCs

Html.jsx - My HTML jsx component that tries to import/require the CSS. This is an isomorphic app (using Fluxbile), hence needing to have the actual HTML as a rendered component. Using the require statement seen in this file, in any part of my application, gives the error described.

I'm stunned that anyone is still using Fluxible at this point. You are referring to https://www.npmjs.com/package/fluxible, right?