Fix default lang bug when React tree doesn't contain withI18next

[isaachinman]

No description provided.

[coveralls]

Coverage remained the same at 77.023% when pulling 0e451c4 on isaachinman:master into 19f5f3f on i18next:master.

[jamuhl]

thank you for looking deeper into it...really appreciate your help.

personal i'm looking into the 16.7 release of react -> guess will bring some changes to next.js too

[isaachinman]

Yup, it probably does. I haven't looked at 16.7 yet, but I might get a chance to this week. Just let me know if you need anything!

[jamuhl]

prepared a react-i18next version based on hooks and suspense (no support for SSR yet) -> if you ever into it you might have a look: #590

[isaachinman]

Nice! I will take a look sometime this week.

[Enalmada]

@isaachinman When I run the latest nextjs example from master, clicking any link appears to do a full page change and flicker. I wanted to look at how you fixed the default lang bug and am worried the solution may being doing something to break routing?

[isaachinman]

@Enalmada Yes, that is correct. The fix caused a regression, which is now also fixed. I plan on doing a complete rewrite of the example pretty soon. You can add your feedback in #609.