Replies: 1 comment
-
There is everything you need out there. I would not expect react-strict-dom to do something about the routing. You should probably have different routing solutions depending on the platform (e.g.: Next for the web, react-navigation for native). So yeah, this involves a part not shared across platforms, but it makes sense as you don't have the same thing available when working on a fullscreen iOS app, or a web page inside a Chrome browser. It does not make sense to try to share this part. Just use different routers. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Mobile and web routers have different needs, mobile routers use stack based navigation. The only routers I know that handle that for react are ionic-router which is full of bugs and react-navigation which has dependencies on RNW and turns off gesture navigation for web.
Beta Was this translation helpful? Give feedback.
All reactions