Top next-i18next issues

Context is broken with react-tree-walker

isaachinman picture isaachinman·14 Dec 2018·27 Comments

<Link> inside <Trans> does not work

ReinoutStevens picture ReinoutStevens·2 Jul 2019·7 Comments
👍5

next-i18next version update - Cannot find module 'next-i18next/middleware'

nataliaroque77 picture nataliaroque77·1 Oct 2020·3 Comments
👍1

Cannot destructure property `components` of 'undefined' or 'null'.

safakcosar picture safakcosar·23 Mar 2020·8 Comments
👍7

i18next doesn't switch to other language, is stucked in the default one

HectorLS picture HectorLS·24 Sep 2019·6 Comments
👍1

Provide fix locale option for Link component.

StarpTech picture StarpTech·6 May 2019·10 Comments

defaultLanguage not working

ScottAgirs picture ScottAgirs·22 Apr 2019·13 Comments

How to combine next-routes & next-i18next Link?

felixmosh picture felixmosh·11 Mar 2019·8 Comments
👍1

Warn: You have not declared a namespacesRequired array on your page-level component: undefined. This will cause all namespaces to be sent down to the cli ent, possibly negatively impacting the performance of your app. For more info, see: https://github.com/isaachinman/next-i18next#4-declaring-namespace-dep endencies

chulphan picture chulphan·16 Jan 2019·7 Comments

Refactor to Typescript

Nelrohd picture Nelrohd·30 Dec 2018·12 Comments
👍5 👎3
 Previous issues
Next issues