react-native-macos/Libraries/ReactPrivate
Nick Gerleman 161b910494 Do not explicitly include ".js" in Library imports (#28311)
Summary:
A few recent imports have explicitly added ".js" to the end of their path. This prevents Metro from resolving platform-specific JS files, e.g. "Foo.android.js" or "Foo.windows.js" instead of "Foo.js".

React Native Windows provides its own implementation of files in a few cases where stock React Native will share them between Android and iOS. We hope to reduce/eliminate these long term, but requiring explicit ".js" files currently breaks us in a couple of places where we have custom implementations.

This change is a quick regex replace of ES6 and CommonJS imports in 'Libraries/" to eliminate ".js".

## Changelog

[General] [Fixed] - Do not explicitly include ".js" in Library imports
Pull Request resolved: https://github.com/facebook/react-native/pull/28311

Test Plan: I haven't done any manual validation of this, but `flow-check` should catch any issues with this during CI.

Reviewed By: cpojer

Differential Revision: D20486466

Pulled By: TheSavior

fbshipit-source-id: 31e1ccc307967417d7d09c34c859f0b2b69eac84
2020-03-17 02:11:53 -07:00
..
README ReactPrivate, an explicit interface between the renderer and RN (#24782) 2019-05-20 07:16:57 -07:00
ReactNativePrivateInitializeCore.js ReactPrivate, an explicit interface between the renderer and RN (#24782) 2019-05-20 07:16:57 -07:00
ReactNativePrivateInterface.js Do not explicitly include ".js" in Library imports (#28311) 2020-03-17 02:11:53 -07:00

README

JS modules in this folder are forwarding modules to allow React to require React Native internals.