Currently, components are automatically hydrated if a re-render is triggered (because a property changes for example). There are two problems with this:
This might not be expected by people using this package?
It is not implemented very elegantly - in order to skip initial render, a timeout is used. But if a (manual) re-render is triggered before the timeout, nothing happens.
Currently, components are automatically hydrated if a re-render is triggered (because a property changes for example). There are two problems with this: