Closed imbhargav5 closed 2 months ago
Your example is broken because you've specified the wrong path in next.config.mjs
. Please make sure to link to your request configuration, not your routing configuration. If you remove the override in the reproduction, then your i18n/request.ts
file is picked up correctly.
I've added https://github.com/amannn/next-intl/pull/1327 to introduce error handling for this case, thanks for the report!
Amazing. Your speed is next level. Thanks for this amazing project good sir!
Awesome, happy to help! 😊
Description
I see
t is not a function
error when I try to use the Link component exported by@/i18n/routing
. My understanding is that the Link component is implemented independently in both server and client component environments and should work in both places. However, I am running into this issue in the server environment and the client environment works fine.Verifications
Mandatory reproduction URL
https://github.com/imbhargav5/next-intl-bug-repro
Reproduction description
Steps to reproduce:
Expected behaviour
There should be no
t is not a function
error in the server side and the Link function should use the current locale from cache and navigate correctly.