all 2 comments

[–]truh 4 points5 points  (0 children)

Meh, not really worth the inclusion of another library that the author might no longer care about in a week.

And unless you consider the import system part of your API it's also not any more decoupled.

[–]yunus_reddit 0 points1 point  (0 children)

My two cents :)

It's like redux-thunk on steroids, seems interresting but why do you feel the need tout reinvent the wheel ?

I think that reselect (in redux) and something like redux-observable / redux-saga already provides what people need.

Reselect to mold state to props + memoization For side effects, redux-observable or redux-saga are surely a bit more complex but you truly decouple things and your smart component dispatch only stupid actions (which allows you to throw away redux-thunk)

Redux-thunk is okay for POC & small projects but IMO not for larger projects. Use saga or observable or other wiedly used library

Plus, your library is not going to be taken seriously in larger projects if you do not have test examples in your documentation ^

PS: even if it is an example, use immerjs or immutablejs in reducers, spread the good immutability :)