i18n Ally Error: TypeError: Cannot read property 'split' of undefined
See original GitHub issueDescribe the bug After a clean install of this plugin I get…
i18n Ally Error: TypeError: Cannot read property 'split' of undefined
Extension Version i18n Ally v1.12.7
To Reproduce Steps to reproduce the behavior:
- Install VSCode
- Install i18n Ally VS Code extension
- Open VSCode
Device Infomation
- OS: Win
- Version: 10
- VSCode Version: 1.42.1
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
i18n Ally Error: TypeError: Cannot read property 'split ... - GitHub
I think I found the problem! From the locale file you provide, I assume you are using Laravel. In Laravel, there is a...
Read more >Cannot read property 'split' of undefined in discord and nodejs ...
"TypeError: Cannot read property 'split' of undefined" basically means that "The value that .split() was called on does not have a .split() ...
Read more >Build error: "TypeError: Cannot read property 'split' of undefined"
I am setting up a quasar project and am getting the above error message (“TypeError: Cannot read property 'split' of undefined”) when ...
Read more >Cannot read property 'clientId' of null-angular.js - appsloveworld
Coding example for the question ERROR TypeError: Cannot read property 'clientId' of null-angular.js.
Read more >typesafe-i18n - npm
A fully type-safe and lightweight internationalization library for all your TypeScript and JavaScript projects.. Latest version: 5.18.0, last published: 15 ...
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
It should be work in v1.12.10. Please check it out 😃
Seems fixed. No errors now, thanks @antfu !