No locale files loaded. Probably there is something wrong with your project config.
See original GitHub issue📣 By @antfu: If you found yourself facing the same warning, please browser the discussion in the following comments first. And if your problem didn’t get solved, please leave a comment with your workspace settings
, i18n ally Output
, and screenshots of your dir structure
.
I would love to help but be sure to provide enough information! Thanks!
Describe the bug No locale files loaded. Probably there is something wrong with your project config.
Extension Version i18n Ally(2.0.9)
Framework/i18n package you are using vue-i18n
To Reproduce Steps to reproduce the behavior:
- open vscode
- The system pops up a dialog box
- No locale files loaded. Probably there is something wrong with your project config.
Device Infomation
- OS: macOS 10.15.4
- Version:
- VS Code Version:1.44.2
Extension Log
Go to View
-> Output
-> i18n Ally
, and paste the content below. You should mask any sensitive information
Screenshots
Issue Analytics
- State:
- Created 3 years ago
- Comments:22 (12 by maintainers)
Top Results From Across the Web
No locale files loaded. Probably there is something wrong with ...
@MaxPeak You are using JS as your locale files, which is disabled by default in v2.0. You will need config: "i18n-ally.enabledParsers": ["js"].
Read more >I18n Ally for Quasar framework internationalization | by Usher
No locale files loaded. Probably there is something wrong with your project config. How to fix this? As you see the message itself...
Read more >vue.js - How can I change the locale of a VueI18n instance in ...
This application has multiple Vue files like a MenuBar.vue, HelpDialog.vue, each pulling from translation.ts for their English translations.
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 >Rails i18n: 3 quick tips and 1 crazy abuse - Justin Weiss
When you build your locale files, you'll probably have some of your keys ... Sometimes, static translations in a yaml file just won't...
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
I was already using JSON files, so the fix above didn’t work. My directory structure is
/src/i18n/languages/{locale}.json
, and I am using vue-i18n.What worked eventually was to remove all i18n-ally settings in User Settings (settings.json) and only add the following setting:
"i18n-ally.pathMatcher": "{locale}.{ext}"
Now it works. Not quite what the migration guide specified, so hope it helps for anyone having the same problem!
Glad to hear it works for you now 😃