[WebStorm] Type error '__VLS_ctx.$t' is of type 'unknown'.

[IgorKha]

Environment

---

• Operating System: Darwin
• Node Version: v22.11.0
• Nuxt Version: 3.14.1592
• CLI Version: 3.17.1
• Nitro Version: 2.10.4
• Package Manager: npm@10.9.0
• Builder: -
• User Config: default
• Runtime Modules: @pinia/nuxt@0.9.0, @nuxt/eslint@0.7.4, @nuxtjs/i18n@9.1.1
• Build Modules: -

---

export default defineNuxtConfig({
  compatibilityDate: "2024-11-01",
  devtools: { enabled: true },

  modules: ["@pinia/nuxt", "@nuxt/eslint", "@nuxtjs/i18n"],
  i18n: {
    debug: true,
    types: 'composition',
    strategy: 'no_prefix',
    defaultLocale: 'en',
    lazy: true,
    langDir: 'locales',
    locales: [
      {
        name: 'English',
        code: 'en',
        language: 'en-GB',
        file: 'en-GB.json',
      },
    ],
  },

  future: {
    compatibilityVersion: 4,
  },

Reproduction

I don't know how reproduce this problem in online services

Describe the bug

With this configuration on a clean project I get this typing error: '__VLS_ctx.$t' is of type 'unknown'.

Additional context

No response

Logs

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 Reproduction starter (v8 and higher)
👉 Reproduction starter (edge)

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[BobbieGoede]

I don't know how reproduce this problem in online services

A Github repo of a minimal reproduction project will be sufficient too 🙏

[IgorKha]

@BobbieGoede yes, this simple repo

https://github.com/IgorKha/nuxt3-i18n-type-repr-issue

thank you!

[BobbieGoede]

@IgorKha
It looks like you have an old release candidate of this module installed (^9.0.0-rc.2), updating to latest (npm i -D @nuxtjs/i18n@latest) should resolve your issue, you may need to refresh lockfiles and/or restart ts language server after installation.

[IgorKha]

@BobbieGoede
unfortunately it didn't work.
What I did.

1. updated as you recommended
2. Run npx nuxi cleanup.
3. Deleted node_modules
4. Restarted the IDE
5. Reinstalled modules npm i
6. Restarted the IDE again.

I also disabled all plugins and deleted the IDE configuration to make sure the problem is not with third-party plugins or settings

[IgorKha]

I found the root of the problem
it's related to this problem, so please forgive me for wasting your time.
tldt: you need to explicitly enable hybrid mode for vue.volar

{
  "vue.server.hybridMode": true
}

vuejs/language-tools#4206

[userquin]

In my case it is copilot plugin:

[MickL]

Hello @BobbieGoede @IgorKha , I am having this issue since "forever". My IDE (WebStorm) is showing $t, $n etc red:

I am on latest @nuxtjs/i18n, 9.2.1.

vuejs/language-tools#4206 seems to be related to VSCode only. Can we reopen?

[BobbieGoede]

@MickL could you provide a minimal reproduction? 🙏

[MickL]

@BobbieGoede Weirdly with the Stackblitz example it works. But I made a reproduction which is basically my project minus everything and there it is reproducable:

https://github.com/MickL/nuxt-i18n-typings

[maxdzin]

@BobbieGoede it can be reproduced with the latest vue-tsc@3.0.0:
https://stackblitz.com/edit/github-jjpn8kps-jtjgrujq

[luke-z]

A workaround is to add vue-tsc to the devDependencies with v2.x.x
Otherwise, nuxt typecheck uses latest