adamscybot

I tried everything here and failed. It was actually something different not documented here. **It was to do with the case sensitivity of the react imports**. In some cases we...

I don't disagree with giving users the ability to configure without code -- but if a function is detected and its called with the right context it gives users like...

Yeh it look sensible. Since babel is the thing that decides what file it is currently looking at, with your proposal, each match that is found it would check if...

Its still broken in Safari 14.0.1.

Trouvble is I want all the constraints back not just key code. You cant get the contraints in the error for rendering later.

Just adding a note here for anyone googling. This package caused a very hard to find memory leak in IE11. This is obviously IE's fault, not the package. But it...

It's very un-react for a component to use DOM API's to reach outside of its own scope.

I think I am seeing this same thing. After much head-banging I can confirm there's definitely some difference in behaviour between "wepback-dev-server" and "webpack-serve". When using `runtimeChunk: 'single'` with "webpack-serve"...

Continuing coversation from apollographql/react-apollo#2059. I got around this by adding a link that overloads `data` with a function that returns the extensions. ```javascript // See https://github.com/apollographql/react-apollo/issues/2059 // Because of this...

Yep sure! I sort of held off as was worried that maybe there's more considerations I don't know about but it appears to be fine. Will raise shortly. Total side...