You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As much as navio has been a great approach to routing in our React Native codebases.
This is a third party library that is mantained by a single person and has not received updates in the last year. For the time being this is just fine since it's properly covering our needs in our codebases but it may grow out of date at some point.
The expo team has released a new way of defining routing in react native expo projects which is called Expo Router
I guess it is worth a shot to see if that is a better approach with the current one we have. Considering that is developed and maintained by the expo core team, and it is readily available for us to use, doesn't seem like a bad option.
Likely we will need to restructure files a bit since this is a file-based routing (similar to Next.js)
The text was updated successfully, but these errors were encountered:
As much as
navio
has been a great approach to routing in our React Native codebases.This is a third party library that is mantained by a single person and has not received updates in the last year. For the time being this is just fine since it's properly covering our needs in our codebases but it may grow out of date at some point.
The expo team has released a new way of defining routing in react native expo projects which is called Expo Router
I guess it is worth a shot to see if that is a better approach with the current one we have. Considering that is developed and maintained by the expo core team, and it is readily available for us to use, doesn't seem like a bad option.
Likely we will need to restructure files a bit since this is a file-based routing (similar to Next.js)
The text was updated successfully, but these errors were encountered: