Next-intl Localization error
Unanswered
Trigg Hound posted this in #help-forum
Trigg HoundOP
I'm trying to use App Router setup without i18n routing approach to do localization in my app but everything fine till I reach this point
then starting to get this error in the console
hree is me i18n.js file
then starting to get this error in the console
hree is me i18n.js file
11 Replies
@Trigg Hound I'm trying to use App Router setup without i18n routing approach to do localization in my app but everything fine till I reach this point
then starting to get this error in the console
hree is me i18n.js file
error happens on either line 45 or 51, there is nothing I can tell with current context
Trigg HoundOP
@Coffee Coke Yeah, I know they cannot get it right but i don't know why despite the imports are correct
maybe its because of the configuration? idk I have never tried setting up without templates
Trigg HoundOP
I don't know actually, I did everything as the documentation said.
@Trigg Hound I don't know actually, I did everything as the documentation said.
could you show me your directory structure?
Trigg HoundOP
oh also, just looked at the docs and should locale prop be passed inside the provider? because in the docs jts not passed
Trigg HoundOP
Yeah, I removed it but didn't solve anything
problem must then be with returned messages inside the getRequestConfig, try adding a few try caches or console logs to see the issue
Trigg HoundOP
Yeah, tried but the problem is that this fucntion seemed to be not called at all it doesn't console.log anything as its not reached