-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Equivalent of react-native-cli #62
Comments
Hapi > express IMHO |
Hope I understand this issue correctly. I'm working on a small project which tries to provide scripts for creating a mixed react-native + react-native-web project here and comments are welcome :) |
Looking at this tutorial it seems that the things needed to do that are different from react-web would be to install React/React-Dom, Webpack, and a dev server. A react-native-web CLI would be useful if it included those things as dependencies and provided a |
Maybe create-react-app would be a good place to start because they're working on having react-native-web be a first class citizen. |
I think that's a good idea! Going to close this. Thanks |
https://facebook.github.io/react-native/docs/getting-started.html#quick-start
React Native has relatively simpler setup compared to contemporary React-based web apps. At the expense of absolute customization comes better ecosystem consistency and fewer barriers to entry. This is something we're intent of improving internally at Twitter too, because we want someone to be able to start building their web app ASAP, rather than doing setup work and making divergent choices.
A web equivalent might include:
Probably a test setup for client and server code? I wrote a bundled package for client-side testing at Twitter for this. One dependency + ~5 lines of code across 2 files and you get: karma, mocha (we go with the tdd ui), sinon, all browsers launchers (inc. browserstack), phantom, jsdom, rerunning of changed tests, and the ability to bundle subsets of your tests. Don't think we want to get into integration testing though.
The text was updated successfully, but these errors were encountered: