Property '$t' does not exist on type on nuxt 4 after upgrade

[makkalay]

Environment

Operating system Windows 10.0.26200 │
│ │ CPU AMD Ryzen 7 xxx/ Radeon xxxGraphics (always not enough cores) │
│ │ Node.js version v25.2.1 │
│ │ nuxt/cli version 3.34.0 │
│ │ Package manager bun 1.3.8 // 1.3.9-1.3.10 has bug that make life hard │
│ │ Nuxt version 4.4.2 │
│ │ Nitro version 2.13.1 │
│ │ Builder vite 7.3.1 │
│ │ Config alias, app, css, devtools, experimental, fonts, i18n, image, modules, nitro, routeRules, runtimeConfig, security, ssr, │
│ │ telemetry, typescript, vite, vuetify │
│ │ Modules @nuxt/eslint 1.15.2, @nuxt/fonts 0.14.0, @nuxt/image 2.0.0, @nuxt/scripts 0.13.2, @nuxt/test-utils 4.0.0, @pinia/nuxt 0.11.3, │
│ │ nuxt-security 2.5.1, vuetify-nuxt-module 0.19.5, @nuxtjs/i18n 10.2.3, @hebilicious/authjs-nuxt 0.3.5 │
│ │

Reproduction

<template>
  <NuxtLink :to="$localePath('index')">{{ $t('home') }}</NuxtLink>
  <NuxtLink :to="$localePath('index', 'en')">Homepage in English</NuxtLink>
  <NuxtLink :to="$localePath('user-profile')">Route to {{ $t('profile') }}</NuxtLink>
  <NuxtLink :to="$localePath({ name: 'category-slug', params: { slug: category.slug } })">
    {{ category.title }}
  </NuxtLink>
</template>

Describe the bug

Property '$t' does not exist on type

Additional context

No response

Logs

[yschroe]

For me this regularly happens whenever a new Vue version is released. I guess it is because some of the @vue/* packages are not automatically updated correctly which results in conflicting types.
Deleting node_modules and the lockfile and then reinstalling again usually solves the problem. Might help in your case as well.