Peter Mikitsh

More context on the rationale for why the `$`-prefix can be useful (emphasis added): > Think of transient props as a lightweight, but complementary API to shouldForwardProp. Because styled-components allows...

@Pajn If you're looking to use WHATWG Streams with libraries expecting Node v2 Streams today, there are projects to help bridge the gap. For example, if you're working with `File`...

@wdavidw By no means is this a complete answer, but I think there's mainstream interest. Days ago, a [Chromium](https://github.com/whatwg/fetch/pull/425#issuecomment-518899855) maintainer stated they're exploring getting ReadableStream integration into the fetch API...

Probably a little early. The specification was last updated [July 29th](https://streams.spec.whatwg.org/). WHATWG Streams are least [partially implemented](https://caniuse.com/#feat=streams) in all evergreen browsers-- Chrome 76 already has some of the classes defined...

@nickmccurdy's solution worked for me. Thanks Nick!

Any updates on this? I've attempted adopting preact, and I'm also using the latest react-helmet, and I noticed this issue.

For my use case, the simplest option was to rewrite my code to use the v4 interface. If you're using v5 of react-helmet, the old API is still supported, so...

@chrisbolin I like the solution you propose because it addresses the issue, but architecturally, shouldn't these problems be the responsibility of the library, probably somewhere in the `VictoryZoomContainer` implementation? It...

@chrisbolin Awesome, thank you! The work around is sufficient for the time being. I opened up dev tools and confirmed the frame rates stays near 60 frames / second.

I've set `devMode` to `true` and have `extractCss` specified. I'm running babel with the `--watch` flag, but my extractCss file doesn't update.