fix useRouter error for expo nextjs 13

[ebg1223]

calling useRouter hook when using nextjs 13 branch leads to an error on expo: unable to find Navigation, instead of simply returning undefined. Using same method as use-route for use-router bypasses this issue so that useRouter hook is only called iff on web.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
solito-s9oj	❌ Failed (Inspect)		Nov 13, 2022 at 7:06AM (UTC)
with-custom-fonts	✅ Ready (Inspect)	Visit Preview	Nov 13, 2022 at 7:06AM (UTC)

2 Ignored Deployments

Name	Status	Preview	Updated
solito	⬜️ Ignored (Inspect)		Nov 13, 2022 at 7:06AM (UTC)
solito-app	⬜️ Ignored (Inspect)		Nov 13, 2022 at 7:06AM (UTC)

[xinha-sh]

@ebg1223 wouldn't this make useRouter functionality redundant on native ?

[ebg1223]

@xinha-sh sorry, not quite sure what you mean. This only changes the behavior of the useParam hook. The problem is, useParam hook calls both useRoute and useRouter, as hooks must not be conditional.

Prior to next13, useRouter would return undefined if next router was not active. With next13, it instead throws an error, which crashes expo.

This change makes it so that if useRouter is called from the useParam hook on native, useRouter will not actually be called. The same functionality exists for useRoute for the native router.

[nandorojo]

i think this looks good to me, i’ll include it in v2

[ebg1223]

@nandorojo Thank you!