Type hinting does not work in Vue SFC template part

[Salmon42]

Vue - Official extension or vue-tsc version

2.1.0

VSCode version

1.92.2

Vue version

Nuxt 3

TypeScript version

5.5.2

System Info

System:
    OS: Linux 5.10 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 7800X3D 8-Core Processor
    Memory: 47.21 GB / 49.59 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v20.14.0/bin/yarn
    npm: 10.8.1 - ~/.nvm/versions/node/v20.14.0/bin/npm

Steps to reproduce

After last update to v2.1.0 the typehinting / intellisense stops working in Vue SFC's template part - everything is inferred to any, even though the given references are correctly declared in <script setup>.

What is expected?

In single previous version 2.0.28, the opened source file looks like this:

What is actually happening?

Link to minimal reproduction

No response

Any additional comments?

To note, I was using Nuxt3 at that time, and the AccomodationCard component was auto-imported into the SFC automatically (through autogenerated directory .nuxt). I haven't tested this behavior on pure Vue3 setup or anywhere else.

My current workaround was to specifically revert the extension to version 2.0.28

[RayGuo-ergou]

Reproduced in neovim too, by checking the log no error throw and can get generic vue proprieties (is, key and ref).

To get workaround in neovim, after downgrade to 2.0.28, have also to pin volar version. see: #4706 (comment)

[Soveilove]

yes.2.1.0 it does not support corresponding function cabinets

[FilePlus]

I also encountered the same problem.

[l246804]

+1

[moonwane]

+1
all globally typed components are now of "any" type

[davidmatter]

Workaround for now: Add the following to your tsconfig.compilerOptions:

"paths": {
      "vue/__globalTypes_3.4_false": ["node_modules/vue/__globalTypes_3.4_false.d.ts"]
}

[liuheo]

+1 all globally typed components are now of "any" type

I also encountered this problem, I lowered the version to v2.0.28 and it worked fine.

[kingyue737]

I upgraded to v2.1.2 but still encountered this issue

[Artles777]

v. 2.2.8 issue too