Emily Janzer bd2c57569b Use require for NativeModules ...

Summary:
Not totally sure if this is the best way to handle this. In Venice if a native module is missing I try to log the name of the module, but I noticed that the error I was getting was getting this:

{F161460962}

Presumably this is because importing from NativeModules looks for `__esModule`, but NativeModules uses `module.export`. So it's trying to access that property on my cpp proxy object, which doesn't exist...? Changing TurboModuleProxy to use `require` seems to fix the problem.

Reviewed By: fkgozali

Differential Revision: D15787508

fbshipit-source-id: 4b9df4e3c179117999fe6de6363edbef427a8263

2019-06-12 16:18:36 -07:00

..

samples

Migrate "Libraries" from Haste to standard path-based requires (sans vendor & renderers) (#24749)

2019-05-08 08:48:59 -07:00

RCTExport.js

Move TurboModuleRegistry (JS) to github

2019-01-04 16:19:43 -08:00

TurboModuleRegistry.js

Use require for NativeModules

2019-06-12 16:18:36 -07:00