From c95fdb0505a01fe5f8980ed67271589ee8e66191 Mon Sep 17 00:00:00 2001
From: Eli White <eliwhite@fb.com>
Date: Wed, 17 Oct 2018 22:17:01 -0700
Subject: [PATCH] Don't use local alias in react-native-implementation

Summary: Nuclide's export detection for modules doesn't resolve local aliases. Lets just export the object directly.

Reviewed By: mostafaeweda

Differential Revision: D10443054

fbshipit-source-id: 880aa1eadff554903eb765d7104ecf3c3b72cbce
---
 Libraries/react-native/react-native-implementation.js | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/Libraries/react-native/react-native-implementation.js b/Libraries/react-native/react-native-implementation.js
index 3941d8fe042215..9138218a2eb4c8 100644
--- a/Libraries/react-native/react-native-implementation.js
+++ b/Libraries/react-native/react-native-implementation.js
@@ -15,7 +15,7 @@ const invariant = require('fbjs/lib/invariant');
 let showedListViewDeprecation = false;
 
 // Export React, plus some native additions.
-const ReactNative = {
+module.exports = {
   // Components
   get AccessibilityInfo() {
     return require('AccessibilityInfo');
@@ -340,5 +340,3 @@ const ReactNative = {
     );
   },
 };
-
-module.exports = ReactNative;