James Please

Yup, I agree @bigsweater. I came around after reading @IceCreamYou 's initial response to this issue (then I dropped off the face of the Earth. Sorry 'bout that :) )...

That sounds like a solid API to me, @IceCreamYou .

> I also thought of another use case: libraries that want to use MainLoop whose users might also use MainLoop. Users would be likely to overwrite the handlers that the...

> This is incorrect. Every module loader I know of caches state the first time a module is loaded. Otherwise, singletons wouldn't be possible You're right about this, and I...

Either approach sounds fine to me.

cc @iansu . This bug is likely causing a considerable amount of frustration with users and may be motivating people switch to alternative build tools. If you haven't already seen...

Cool! I took a quick look to see some differences. Here's what I saw: - render-props-compose already supports object syntax. I have it as an open issue ( https://github.com/jmeas/react-composer/issues/23 )...

My current plan is to: 1. reverse the render order 2. add some sort of prop that behaves like `functional` 3. **not** add a `reverse` prop This will be done...

@gnapse item 2 refers to what you described as: > a feature to allow each component in the chain to access the props of the previous one. It can be...

Yup, I wouldn't worry too about the commits. We can always use `git rebase` to clean em up before merge!