**Do you want to request a *feature* or report a *bug*?**

Bug

**What is the current behavior?**

React Native for Web was broken by 16.5 as describe [here](https://github.com/necolas/react-native-web/issues/1096) due to this change https://github.com/facebook/react/pull/13539

**What is the expected behavior?**

Release a version of React that exports the EventPluginHub.

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**

Worked in 16.4
* form of a mapping from integer (touch `identifier`) to touch target. This is
 * encoded in array form. Because of this, it is possible for two separate
 * touches (meaning two separate indices) to have the same touch target ID -
 * this corresponds to real world cases where two separate unique touches have
 * the same target. These touches don't just represent all active touches,
 * rather it also includes any touches that are not active, but are in the
 * process of being removed.
 * @param {Array<NodeHandle>} changedIndices Indices of `allTouchHandles` that
 * have changed.
 * @return {object} Config data used by test cases for extracting responder
 * events.
 */
const startConfig = function(nodeHandle, allTouchHandles, changedIndices) {
  return _touchConfig(
    'topTouchStart',
    nodeHandle,
    allTouchHandles,
    changedIndices,
    nodeHandle,
  );
};
/**
 * @see `startConfig`
 */
const moveConfig = function(nodeHandle, allTouchHandles, changedIndices) {
  return _touchConfig(
    'topTouchMove',
    nodeHandle,
    allTouchHandles,
    changedIndices,