You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, I encountered some problems while using i18n-ally for internationalization in Vue projects. I'm sharing my experience here, hoping it might help other developers facing similar issues.
Problems Encountered
In a Vue 2 project created with Vue CLI, language files (src/lang/zh.js and en.js) loaded normally.
In a Vue 3 project created with Vite, language files failed to load with the same configuration.
The problem was resolved after changing the language files to JSON format.
In VSCode, i18n variables don't display their actual values.
Using Chinese as i18n keys in the Vue 2 project led to more issues.
Key Finding
Strongly recommend using JSON format for language files. This can avoid many potential loading problems.
Current i18n-ally Configuration
Recently, I encountered some problems while using i18n-ally for internationalization in Vue projects. I'm sharing my experience here, hoping it might help other developers facing similar issues.
Problems Encountered
Key Finding
Strongly recommend using JSON format for language files. This can avoid many potential loading problems.
Current i18n-ally Configuration
Use JSON format for language files.
The text was updated successfully, but these errors were encountered: