Using `next-international` for i18n support breaks my tRPC config.
I am trying to add translation support to my app (https://expenses.rmallafre.com), and everything was going fine up until a client component needed to do some tRPC queries. I see that the route it hits is a localised route (as in:
/en/api/trpc/... rather than just /api/trpc/...).
I have no idea what I need to change anymore to get this to work. The code is available at: https://github.com/nikensss/is-it-that-much/tree/iitm-22-localisationGitHub
GitHub - nikensss/is-it-that-much at iitm-22-localisation
Contribute to nikensss/is-it-that-much development by creating an account on GitHub.
4 Replies
Hi! I am using next international as well. I place /api/ outside of [locale]
GitHub
kodix-turbo/apps/kdx/src/app at main · dBianchii/kodix-turbo
Contribute to dBianchii/kodix-turbo development by creating an account on GitHub.
One question: why are you using next-international, in the midst of other packages?
No particular reason, it was the one I saw that seemed to have the simplest steps to get it up and working. I'm gonna check your repo in a bit, thanks a lot for the help!
I also keep /api outside of /locale, btw