Replies: 3 comments
-
|
Nearly forgot: I also tried it this way: src/i18n/index.tsimport { createI18n } from 'vue-i18n';
import messages from '@intlify/unplugin-vue-i18n/messages';
// import de from './messages/de.json';
// console.log(de);
// eslint-disable-next-line @typescript-eslint/naming-convention
export const SUPPORT_LOCALES = ['de'];
export const i18n = createI18n({
locale: 'de',
fallbackLocale: 'de',
legacy: false,
messages,
}); |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Somebody an idea? :/ |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Should this ever happen to somebody: check if you by mistake put a number as number instead of as string for testing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
we're currently starting a new project and we're experiencing something seriously strange with vue-i18n.
We're using the current versions of vue, vue-i18n, vite and also the "unplugin" vue-i18n plugin for vite. For testing we added one locale message, overwrite it in the local scope of the vue component and try to display it. But no matter what we try, We get the message the "key" couldn't be found.
The most weird thing is and I tried it in Firefox as well as in Chrome, I can see the messages in Vue dev tools.
Does somebody have any idea what could be the problem?
Screenshot Firefox console
Screenshot Vue Devtools - I18n Resources - global scope
Screenshot Vue Devtools - I18n Resources - local scope
package.json
{ "name": "@snow/frontend", "version": "2.0.0-dev", "private": true, "scripts": { "dev": "vite", "build": "run-p type-check build-only", "preview": "vite preview", "build-only": "vite build", "type-check": "vue-tsc --noEmit -p tsconfig.app.json --composite false", "lint": "eslint . --ext .vue,.js,.jsx,.cjs,.mjs,.ts,.tsx,.cts,.mts --ignore-path .gitignore" }, "dependencies": { "@fortawesome/fontawesome-pro": "^6.4.0", "@fortawesome/fontawesome-svg-core": "^6.4.0", "@fortawesome/pro-duotone-svg-icons": "^6.4.0", "@fortawesome/pro-light-svg-icons": "^6.4.0", "@fortawesome/pro-regular-svg-icons": "^6.4.0", "@fortawesome/pro-solid-svg-icons": "^6.4.0", "@fortawesome/pro-thin-svg-icons": "^6.4.0", "@fortawesome/sharp-light-svg-icons": "^6.4.0", "@fortawesome/sharp-regular-svg-icons": "^6.4.0", "@fortawesome/sharp-solid-svg-icons": "^6.4.0", "@fortawesome/vue-fontawesome": "latest-3", "@intlify/unplugin-vue-i18n": "^0.11.0", "@popperjs/core": "^2.11.8", "@vueuse/core": "^10.1.2", "axios": "^1.4.0", "bootstrap": "^5.3.0", "pinia": "^2.0.36", "sass": "^1.62.1", "vue": "^3.3.2", "vue-i18n": "9", "vue-router": "^4.2.0" }, "devDependencies": { "@intlify/eslint-plugin-vue-i18n": "^2.0.0", "@rushstack/eslint-patch": "^1.2.0", "@tsconfig/node18": "^2.0.1", "@types/bootstrap": "^5.2.6", "@types/node": "^18.16.8", "@typescript-eslint/eslint-plugin": "^5.59.9", "@typescript-eslint/parser": "^5.59.9", "@vitejs/plugin-vue": "^4.2.3", "@vue/eslint-config-typescript": "^11.0.3", "@vue/tsconfig": "^0.4.0", "eslint": "^8.39.0", "eslint-config-xo": "^0.43.1", "eslint-config-xo-space": "^0.34.0", "eslint-config-xo-typescript": "^0.57.0", "eslint-config-xo-vue": "^3.1.23", "eslint-plugin-vue": "^9.11.0", "npm-run-all": "^4.1.5", "typescript": "~5.0.4", "vite": "^4.3.5", "vue-tsc": "^1.6.4" } }yarn.lock
vite.config.ts
src/main.ts
src/i18n/index.ts
src/i18n/messages/de.json
{ "app": { "test": 123 } }Vue component
Beta Was this translation helpful? Give feedback.
All reactions