Idea: Expo Template Support

[hirbod]

This boilerplate is send from heaven to me.
I was thinking about a good structure and if it makes sense to use react-query with zustand and you proofed that it is in fact a good idea.

I would recommend to also provide this as an expo template, since a lot of people really don't like to go vanilla rn.

I mean, it's not a big issue to copy everything to an expo structure, but would be nice to have this as a ready template.

Great work, beautiful setup, I really like it!

[victorkvarghese]

Never had a chance to use expo yet. Will try to see if i can get something ready

[hirbod]

I can just tell you: forget everything you thought you know about it. Since SDK 41 (now at 43), Expo just reached another level with EAS Build, Custom Dev Clients. I'll promise you'll love it and never look back!

P.S: you don't need to call enableScreens() anymore with react-navigation.
Also would recommend you to have a look at
import { createNativeStackNavigator } form "@react-navigation/native-stack"

[Dave-Wagner]

+1 for Expo support.

[consciouscoder]

+2 for Expo support 🙏

[victorkvarghese]

Hi,

I have added another branch #expo-variant

Let me know if this helps or there is a better way to handle expo templates

CC: @hirbod @consciouscoder @Dave-Wagner

[devh2t]

Nice work Victor, amazing work & i appreciate it.

So after running the demo ,it work fine but when i try to use the boilerplate & rename the projet using react-native-rename

,i got an error :

`Invariant Violation: "RNZustandBoilerPlate" has not been registered. This can happen if:

• Metro (the local dev server) is run from the wrong folder. Check if Metro is running, stop it and restart it in the current project.
• A module failed to load due to an error and AppRegistry.registerComponent wasn't called., js engine: hermes`

Can you check this issue plz?

[victorkvarghese]

@devh2t it's working for me, make sure you close server after you rename.