Put back React Native

[steida]

• Probably in /screens dir
• Rethink (again) universal UI library. Common base components I have, or reactxp, or react-native-web? I don't know yet. What is the most pragmatic? Update: react-native-web.

[steida]

vercel/next.js#3018

[steida]

Hmm, it seems we can not have one shared / unversal package.json anymore. React Native Flow settings etc. So, it seems, we have to have two separated projects.

[steida]

Hmm, also React Native seems to be unable to import file outside of /native directory.

[steida]

So I don't know how to share code across Next.js and React Native without two package.json files and some symlinks. One package.json file would be ideal, but it seems to be impossible as well.

Maybe, some kind of private NPM could work. Maybe.

[steida]

How ReactXP solves it? Hmm https://github.com/Microsoft/reactxp/tree/master/samples/TodoList

[msand]

How about a lerna mono repo? Separate package.json files might sometimes be useful e.g, if independent parts of native/web need different version of the same package. Or if someone only works on parts of the project etc.

[msand]

React Native should be able to import external components. I had a working proof-of-concept based on the old Este and RNWeb in may last year: msand@9ad2869

[msand]

I just remembered, I used a universal project with Next.js and React Native to compare and fix svg spec conformance of react-native-svg. I just updated the versions and made sure it still starts:
https://github.com/msand/newproject

[steida]

@msand Thank you. But it's without working .flowconfig.

[msand]

Ah yeah, that's probably true, didn't test that.

[steida]

I fixed it. Thank you for your help.

[msand]

Great! Looking forward to the Next (pun intended) version 😄