Closed cliedeman closed 4 years ago
Hi @cliedeman. Thanks for your PR!!
Is there multiple cases that uses this kind of extensions? Because we at Mendix didnt see that often. You can in this case extend your current webpack configuration and make it work for your case.
Hi There.
It's a standard I have seen in a few projects. A quick search in a react-native project of mine got these results:
./react-relay/lib/relayUnstableBatchedUpdates.native.js
./react-native/node_modules/fbjs/lib/Promise.native.js
./react-native/node_modules/fbjs/lib/Promise.native.js.flow
./metro/node_modules/fbjs/lib/Promise.native.js
./metro/node_modules/fbjs/lib/Promise.native.js.flow
./react-native-screens/src/screens.native.js
./fbjs/lib/Promise.native.js
./fbjs/lib/Promise.native.js.flow
It does result in a pretty obscure error that is hard to track down.
In my case
Error could not resolve screens.js
@cliedeman I would like to inform you this will be published today over version 8.6.0 of the tools
Thanks!
Allow compilation with libraries that use .native.js
Otherwise uncompiled source code ends up in the bundle
Example: https://github.com/kmagiera/react-native-screens/blob/master/src/screens.native.js