Use hydrate() instead of render()

[wingleung]

As of React 16 a new method is available for hydrating server side rendered HTML on the client side, .hydrate().

How should we address this with hypernova-react? Do we create a separate branch to implement new features from React 16 and up? or do we merge to the current master with backward compatibility?

[goatslacker]

We can publish a breaking change with the new behavior.

[ljharb]

That would close off pre-v16 support; we need to find a way to add this that's semver-minor.

[goatslacker]

That would close off pre-v16 support

We can backport fixes if necessary and this library doesn't change much so it's safe to do unless there's a non-gross way to semver-minor this.

[ljharb]

Let's exhaust our options to do it semver-minor tho, before drawing a line in the sand.

[wingleung]

@ljharb @goatslacker made it a semver minor change so it's backward compatible. Also reverted the package version, let you guys handle the version bump. wingleung@70f466c

[ljharb]

The peer deps on react and react-dom need to continue allowing 0.14 and v15, as well as adding in 16.

Please feel free to submit the PR and we can review there!

[ljharb]

Closed in #30.