-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Is this repo dead? #3846
Comments
Yes, but the dream is still alive. Check out Expo Router if you want a clean routing system. |
@nabilfreeman is there an alternative to Expo Router for bare react native projects? |
Plain So following the instructions here is your best bet: https://reactnavigation.org/docs/getting-started It is possible to manage your screens in a declarative way by creating a single stack navigator, declaring all your screens in some sort of config file and looping through it to embed all the screens inside the stack. I personally really hate picking up a project with There are some limitations such as not being able to display modal type screens etc. but you can get pretty far. Also if you need web support where you can refresh the page without losing your props then param based screen names is required which makes setup a bit trickier. Honestly if you want a clean managed experience it's hard to beat Expo Router. Consider setting up a managed Expo environment and try moving your code in and see if everything still works. |
I see many PRs & issues for simple things like updating dependancies. I'm assuming this project has been abandoned. If so are there maintained forks?
The text was updated successfully, but these errors were encountered: