Open
Description
Reporting a bug?
The global variable "$t" show issue 'Property '$t' does not exist on type' in vue template
My ./i18n/index.ts files :
import { createI18n } from 'vue-i18n';
import fr from "./locales/fr.json";
type MessageSchema = typeof fr
export default createI18n<[MessageSchema], 'fr'>({
allowComposition: true,
locale: import.meta.env.VITE_DEFAULT_LOCALE,
fallbackLocale: import.meta.env.VITE_FALLBACK_LOCALE,
legacy: false,
messages: {
'fr': fr,
},
})
My main.ts file :
import { createApp } from 'vue';
import { createPinia } from 'pinia';
import i18n from "./i18n";
import App from './App.vue';
import router from './router';
import './index.css';
const app = createApp(App)
app.use(i18n)
app.use(createPinia())
app.use(router)
app.mount('#app')
My template file :
<nav class="flex flex-row mx-2 m-0.5">
<RouterLink class="px-1" to="login">{{ $t("auth.login") }}</RouterLink> /
<RouterLink class="px-1" to="register">{{ $t("auth.register") }}</RouterLink>
</nav>
Expected behavior
No issue :D
Reproduction
- create new vue3 project
- install "vue-i18n": "^9.3.0-beta.17",
- create json files
- use $t in template
System Info
System:
OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
CPU: (4) x64 Intel(R) Core(TM) i5-7300U CPU @ 2.60GHz
Memory: 6.79 GB / 15.50 GB
Container: Yes
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 18.16.0 - /usr/bin/node
npm: 8.19.1 - /usr/local/bin/npm
Browsers:
Chrome: 113.0.5672.92
Firefox: 113.0.1
npmPackages:
@intlify/unplugin-vue-i18n: ^0.10.0 => 0.10.0
@vitejs/plugin-vue: ^4.2.1 => 4.2.2
@vitejs/plugin-vue-jsx: ^3.0.1 => 3.0.1
@vue/eslint-config-prettier: ^7.1.0 => 7.1.0
@vue/eslint-config-typescript: ^11.0.3 => 11.0.3
@vue/tsconfig: ^0.3.2 => 0.3.2
vite: ^4.3.4 => 4.3.5
vue: ^3.2.47 => 3.3.1
vue-i18n: ^9.3.0-beta.17 => 9.3.0-beta.14-77e850b
vue-moment: ^4.1.0 => 4.1.0
vue-router: ^4.1.6 => 4.2.0
vue-tsc: ^1.6.4 => 1.6.4
Screenshot
No response
Additional context
No response
Validations
- Read the Contributing Guidelines
- Read the Documentation
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussions