VScode cannot use command+click to jump to Vue3's custom component in MacOS

wjw020206 commented 8 months ago

Describe the bug

For the same project, I can use ctrl+click to jump to the corresponding .vue file through the custom component name in Windows 10. However, I cannot use command+click to jump in MacOS. I have tried reinstalling VScode and Open other projects and the problem still exists.I use unplugin-vue-components to automatically import components.components.d.ts is generated.The project can run normally.

The display type is displayed when running under the windows version. However, the type of the custom component in mac displays any.TS or JS function methods and native tags such as div can be jumped, but custom components cannot be jumped, such as el-button.

Windows:

MacOS:

what i expected： Use command + click on MacOS to jump to the .vue file of the corresponding custom component

System Info

- VScode version：1.84.0(arm)
- system version：MacOS Ventura 13.6
- unplugin-vue-components: 0.25.1

Used Package Manager

pnpm

Validations

[x] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[x] The provided reproduction is a minimal reproducible of the bug.

wjw020206 commented 8 months ago

Please do not close this question. My project is running normally, so I cannot provide a test project. For me, I still cannot jump when I create a new project.

wjw020206 commented 8 months ago

The problem is solved. It is a problem with the Vue Language Features (Volar) plug-in version. Version 1.8.22 has a BUG and cannot display the type of custom components. Just reduce the version to 1.8.11.

mbrgm commented 7 months ago

@wjw020206 Can you provide a link to the issue describing the bug?

wjw020206 commented 7 months ago

你能提供描述错误的问题的链接吗？

sure. https://github.com/vuejs/language-tools/issues/3724

Leovenn commented 7 months ago

Yes, I also had the same problem, the problem has been solved after demotion, thank you @wjw020206

unplugin / unplugin-vue-components