setting defaultLanguage to something other than 'en' breaks page after Update to 0.23.0
See original GitHub issueHi, after updating to Version 0.23.0 I had to disable serverLanguageDetection
. If it is enabled, you get the following error when visiting the page:
TypeError: this.language.toLowerCase is not a function at I18n.loadResources (xxx/node_modules/i18next/dist/commonjs/i18next.js:209:42)
Issue Analytics
- State:
- Created 5 years ago
- Comments:20 (16 by maintainers)
Top Results From Across the Web
setting defaultLanguage to something other than 'en' breaks ...
Hi, after updating to Version 0.23.0 I had to disable serverLanguageDetection. If it is enabled, you get the following error when visiting ...
Read more >Change the default input language for Windows
Click Start > Control Panel. Under Clock, Language, and Region, click Change keyboards or other input methods. Note: If you don't see Clock,...
Read more >0.23 Upgrade Guide - Vector.dev
An upgrade guide that addresses breaking changes in 0.23.0.
Read more >How to Setup Your Python Environment for Machine Learning ...
In this tutorial, we will cover the following steps: Download Anaconda; Install Anaconda; Start and Update Anaconda; Update scikit-learn Library ...
Read more >Keyboard Control - mpv.io
The following listings are not necessarily complete. See etc/input.conf in the mpv source files for a list of default bindings. User input.conf files...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
7be2b97
@isaachinman Again, sorry for the confusion, but I believe that what @johnrackles is experiencing is due to what #139 will fix. I just didn’t know, once we merged #139, if another bug would surface. I don’t think that @johnrackles is doing anything wrong, so it’s not a case of user error.