Michael Ridgway
Michael Ridgway
I added this to the config because I am also at a company that has an internal registry and I routinely forget to specify the correct registry when publishing this...
This sounds like an invalid component type is being passed to `hoistNonReactStatics`.
Interesting. I'm looking through the version history to see if there were any bugs in 2.5.x that may have been fixed by 2.5.5. As far as I see, I think...
It's not. The API still uses `registerFetcher`.
Based on #448, these changes should probably move scroll state in a store rather than in the history state.
Right you are. This should definitely be supported. The line in routr that you pointed out just needs to pass `options` in as the third argument. These `options` are already...
That's odd. Looks like this is the behavior of functions that use default parameters. Let me look in to whether this is new behavior from babel and whether we could...
Opened https://phabricator.babeljs.io/T7377 to follow up with Babel team.
After further investigation, this may be how ES6 spec works with default parameter values. We may have to find another solution for this internally.
So the only way to mitigate this that I can see is to check the return value against `undefined`. I'm not sure if there are valid cases where `undefined` could...