Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No hover popups and suggestions are broken #3923

Closed
mattersj opened this issue Mar 1, 2024 · 4 comments
Closed

No hover popups and suggestions are broken #3923

mattersj opened this issue Mar 1, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@mattersj
Copy link

mattersj commented Mar 1, 2024

I've tested the new version on a project with ~5000 files written in plain Composition API (without <script setup>) and it seems like neither suggestions nor hover type popups work in my case.

Hover (props are typed and it had worked before):
image

Autocompletion works the same way both in template and script showing me some internal stuff and nothing related to an actual type:
image

Worth mentioning that this can only be reproduced in *.vue files, .*ts files are fine.

@mattersj
Copy link
Author

mattersj commented Mar 2, 2024

One more thing: there's an error at the end of the file (right after closing <style> tag) with a lot of similar internal codegen errors:
image
image

@so1ve so1ve added the bug Something isn't working label Mar 2, 2024
@johnsoncodehk
Copy link
Member

I haven't been able to reproduce the issue yet, but just in case, check if you have disabled the "TypeScript Vue Plugin (Volar)", which may cause conflicts with 2.0.

@mattersj
Copy link
Author

mattersj commented Mar 2, 2024

@johnsoncodehk That's the first thing I did during updating, I only have the new Vue - Official extension updated to the latest 2.0.2 version right now.
I've also tested how it works on other projects of different sizes and there are the same errors at the end of the file, even if I create a new file and start writing some basic stuff it gives me 0 suggestions right away - even for built-in objects like Math.
image

What's interesting though, is that among those errors at the end of the file I can see actual errors from my code and if I fix all of them the red squiggly line may disappear (but if the template has at least 1 expression it'll be still there - Block-scoped variable '__VLS_3' used before its declaration.ts-plugin(2448))

Here's the output I can see right after reloading the window:

[Vue Named Pipe Client] Error: connect ECONNREFUSED /tmp/vue-tsp-6155
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '/tmp/vue-tsp-6155'
}
[Vue Named Pipe Client] Error: connect ECONNREFUSED /tmp/vue-tsp-6155
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '/tmp/vue-tsp-6155'
}
[Vue Named Pipe Client] Error: connect ECONNREFUSED /tmp/vue-tsp-6155
    at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1495:16) {
  errno: -61,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '/tmp/vue-tsp-6155'
}

@johnsoncodehk
Copy link
Member

See #3942

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants