Bruno Dias

@honeymaro Looks interesting. Can you test locally with react 16.3+, please? I think 16.3+ should be an ok version to support, and, deprecate the rest.

And react 17, please.

Grande lavoro, @honeymaro. We are going to take some time to stress test this one before we merge, so bear with us. cc @doeg

Just to remind that `setState(state, callback)` is a legacy way to update state. Not sure if there are any incompartibilities with the new react state system. Pointing this out, because...

I'm against dropping support if it's not necessary. But I also don't have a plan right now. Maybe, first, we need to understand what's going on with #1090 to see...

But I also wouldn't oppose if we can speculate on the adoption of versions 16.3+ (yep, exactly 16.3 up)

I think I'm being super defensive about this. Maybe, the obsolete class component is dragging this project down. It'd be nice to set a millestone for this changes as we...

jsdom (used by jest) is ok for basic simulations of DOM and rendering, but it's better to use a real browser. I guess any test runner that can run on...

I was trying to get "jasmine-browser-runner" to work, but I was also giving up on it. I'll check it out.

Before we tackle this, we (I mean I) need to finish the build system. I did some progress on that, only need to build the pre-compiled lib and the examples.