Create project with bare react-native have expo commands about ignite HOT 7 CLOSED

@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

from ignite.

When trying to run then having this error

from ignite.

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

from ignite.

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?

from ignite.

@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

from ignite.

Ohh thanks @frankcalise
Last question that concerns me about choosing Expo, if going through the Expo CLI route, it also means to use all it's tools, harder (or impossible) to change some native code as needed for some third party libs, and deploying to the stores is through the EAS being, and being vendor lock to it?
Or maybe I'm missing something since the new versions of Expo?

from ignite.

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!

from ignite.