Uncaught TypeError: Cannot read property 'options' of undefined at new Translate (translate.js:63)
See original GitHub issueI am not sure why this error is happening. Looks like something to do with the configuration of i18n.
The line at translate.js:63 is:
namespaces = namespaces || _this.i18n.options.defaultNS;
Where do the i18n options get configured? Am I configuring something wrong with my reducer?
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Jest error: TypeError: Cannot read property 'options' of ...
The error has to do with react-i18next not being configured correctly in your testing environment. translate() wraps your component and is ...
Read more >Error: Uncaught [TypeError: Cannot read property 'options' of ...
Uncaught TypeError: Cannot read property 'options' of undefined at new Translate (translate.js:63) · Issue #31 ...
Read more >Uncaught TypeError: Cannot read properties of undefined ...
Hi, i have this kind of error in two my site with 6.1 Elementor pro version. Your tool is required for Elments Elementor...
Read more >cannot read properties of undefined (reading 'get') nestjs
When i try to leftJoin and load all products of a category I get error: TypeError: Cannot read properties of undefined (reading 'joinColumns')....
Read more >ANGULAR 13 TypeError Cannot read property of undefined
In this tutorial, we will see a most common error faced by the Angular developers named as " TypeError Cannot read property of...
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 FreeTop 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
Top GitHub Comments
Is your component wrapped in a I18nextProvider?
What did it for me was exactly what @admangum suggested, literally wrap your component like so
where
i18n
would be youri18nConfig
. Not sure how helpful this is, but just wanted to add a comment in case it is to someone.