-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Create project with bare react-native have expo commands #2675
Comments
Hi @trynx - bare in this case means you'll manage the native code yourself. You'll still have Expo dependencies, though. We should make this more clear, however. If you're looking for a version of Ignite that has absolutely no Expo dependencies, you can clone this (although not inline with the latest version of Ignite): https://github.com/frankcalise/ignite-vanilla-template |
Hi @frankcalise :) Sorry for the confusion, in this context when I said "bare", I'm meaning of launching it with react-native, but it's fine on using expo libs. I'm right now using an older version that I created around a year ago, and wanted to move all my logic to a newer version of ignite because iOS stopped compiling on the old version... so while testing the new ignite version found out about this... Eventually, will using expo as a launcher affect the end product? Of bundling the code with Android Studio and xcode, and not using Expo as the production launcher? |
@trynx Ah ok understood, thanks for clearing that up. I haven't tried using the RN CLI much in an Expo project. You might look to undo a few steps from here: https://docs.expo.dev/bare/installing-expo-modules/#optional-use-expo-cli-for-bundling Adopting the Expo CLI has it's benefits though, listed here: https://docs.expo.dev/bare/using-expo-cli/#why-expo-cli-instead-of-npx-react-native |
Ohh thanks @frankcalise |
@trynx You do not have to worry about third party libs with Expo, you are free to choose any lib you find along the way. That's that great part about it. You can also build locally via the EAS command line, you don't have to use their service in the cloud. Read [these docs] for more info: https://docs.expo.dev/build-reference/local-builds/ You can also build with Android Studio/Xcode like normal as well. Here's a post similar to yours you can reference: https://forums.expo.dev/t/using-expo-managed-workflow-without-eas/69893 |
Going to close this as I believe we have covered your questions! If you have any further questions, feel free to open them up on the Discussions board here or come join our Community Slack Also Expo has a Discord where you can get tons of answers as well! |
Describe the bug
When creating a new project and using the manual configuration, did it with bare (not expo) react-native, in the package.json the commands for
start
,ios
andandroid
included expo run and not react-nativeExpected
Got
Ignite version
9.6.3
Additional info
Full terminal logs when creating app
The text was updated successfully, but these errors were encountered: