Replies: 2 comments 2 replies
-
simple fix to my above mistake export function useTranslationClient(
lng: LanguageOptionsType | undefined,
ns: string | string[],
options?: UseTranslationOptions<undefined>,
) {
...
const { t, i18n } = useTranslationOrg(ns, { ...options, lng, nsMode: 'fallback' }) // <--- ensure to pass in lng |
Beta Was this translation helpful? Give feedback.
1 reply
-
@adrai any suggestions on this ? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have followed the Next14 app directory guide and this works great. However, when I open my app with
.../fr/...
in the URL, rather than.../en/...
(which is the fallback language) - i getUncaught Error: Text content does not match server-rendered HTML.
Any ideas/suggestions? When swapping between the locales, there is no issue. It is just on the initial load as the server has
en
whereas the client hasfr
/i18n/index.ts
/i18n/client.ts
/i18n/settings.ts
Server example
Client example
Beta Was this translation helpful? Give feedback.
All reactions