Nikolay

@tizmagik I looked at your library description and seems like it's no different from `react-helmet` because it only works with `renderToString()` which is not asynchronous.

> each array is unique to each request In `react-helmet` it's the same: only a single request is being rendered at any given time because `renderToString()` is not asynchronous. >...

@tizmagik Server-side asynchronous rendering is already there while client-side asynchronous rendering will be enabled in future versions. See https://hackernoon.com/whats-new-with-server-side-rendering-in-react-16-9b0d78585d67

@tizmagik They **are** enabled on the server side

I mean, asynchronous rendering is working but your library isn't: it's still synchronous on the server without the benefits of being asynchronous.

@tizmagik No PR can fix that, so it would have to be a completely different library.

> You can use `ReactDOMServer.renderToNodeStream` in order to test out your library with streaming. There's no need for tests because I can already tell you that it won't work >...

> I think your use case is different. My use case is like everybody else's > the `` tags will be eventually consistent on the client because the client-rendering will...

> the tags will be eventually consistent on the client because the client-rendering will update the head block. > That's another story and that might be even a viable approach....

@goatslacker It's unclear how do you define "that point" because as `react-helmet` goes `` tags can be inserted anywhere including the footer of the page so I see no "middle...