Fix for unsupported platforms

[brunolemos]

Fixes #13 for real
Fixes react-navigation/react-navigation#5004

Use different index.js files for supported and unsupported platforms.

Tested on iOS and on an existing web project that uses react-navigation.

---

Necolas explained here that this import should not be on any file that runs on web: necolas/react-native-web#507 (comment)

[kmagiera]

Thanks @brunolemos This is 💯

[kmagiera]

hey @brunolemos I was just testing it and it appears this just disables screens completely on mobile. The reason is that packager picks screens.js first which does not include any references to native containers. Would it be ok if I rename screen.js -> screens.web.js?

[kmagiera]

I actually went ahead and made these changes (now we only have screens.web.js and screens.native.js in src/)

I published it on NPM under 1.0.0-alpha.14, do you mind testing this with your react native web project when you get a minute @brunolemos ??

[brunolemos]

The reason is that packager picks screens.js

This is weird, the default packager is supposed to prioritize .xxx.js over .js.

But ok, just tested your changes and it worked on web so all fine!

The way you did is cleaner, but I avoided doing this way because .native.js will also run on some other platforms like Windows (I think), and because now the fix is only targeting web specifically, not a fallback for "all unsupported platforms".

[kmagiera]

Thanks for checking!

I wouldn't be concerned about other native platforms as long as they have requireNativeComponent method (I think only web is missing that). When the native component isn't available we are handling that gracefully as this package is not meant just yet to be obligatory. So there are people who don't have it installed and the native views are not available in which case we fallback to using Views.