IntelliSense is not working

[DenisOstr]

IntelliSense doesn't work. Doesn't show what's in the component, nor does it suggest component names in autocomplete (Nuxt UI installed)

What I've already tried (Did not help):

• Change extension version (tried all versions)
• Reinstall the extension
• Install a different version of VSCode (1.88)
• Reinstall VSCode
• Disable all extensions and enable only vue - official

Possibly related things:

By TypeScript

By Vue Language Server

Extension: v2.0.16 VSCode: v1.89.0 OS: Windows 11 Framework: Nuxt 3

[ra1vvxn]

Same here after the extension update I'm getting no linting at all, no suggestions/IntelliSense for autocomplete it doesn't recognize anything.

• Extension: v2.0.16
• VSCode: v1.89.0
• OS: Windows 11
• Framework: Quasar

Is there any temporary workaround? maybe reinstalling previous version and prevent it from updating?

[edarblanco]

I have the same problem, just going back to version 2.0.14 solves it, version 2.0.15 is also compromised

[DenisOstr]

I tried all the versions that are available on the marketplace. Did not help.

[ra1vvxn]

Yo this is so weird I want to say something but first, did you try using any VPN or proxy to another network? Like I mean to fix it. try and tell me.

Because I'm guessing something like all three of us who are talking about this here are from certain countries, using VPN worked for me the ts-plugin or the vue plugin loads the IntelliSense like insiders also wont be loaded if I don't use VPN

[DenisOstr]

This sounds very strange. How changing the network helps the extension, which in theory works offline. Actually, as expected, VPN didn’t help at all.

[ra1vvxn]

Yeah you are right, I know this is nonsense, but for me choosing insider versions also wont work without changing my ip addr.

[DenisOstr]

Are you talking about the insider version of the extension or VSCode? I'm just not really sure what the problem is in the editor or in the extension

[johnsoncodehk]

Can you clone https://github.com/johnsoncodehk/volar-starter and reproduce the problem locally?

If yes, can you reproduce this problem for https://github.com/johnsoncodehk/volar-starter in GitHub Codespaces? If no, can you reproduce this problem for you project in GitHub Codespaces?

[ra1vvxn]

@DenisOstr the insider version of this vue extension!

[DenisOstr]

Can you clone https://github.com/johnsoncodehk/volar-starter and reproduce the problem locally?

If yes, can you reproduce this problem for https://github.com/johnsoncodehk/volar-starter in GitHub Codespaces? If no, can you reproduce this problem for you project in GitHub Codespaces?

I'll try this

[ra1vvxn]

Can you clone https://github.com/johnsoncodehk/volar-starter and reproduce the problem locally?

If yes, can you reproduce this problem for https://github.com/johnsoncodehk/volar-starter in GitHub Codespaces? If no, can you reproduce this problem for you project in GitHub Codespaces?

Sure, can't right now but I'll also try later

[arielkern]

Same issue here. Seems related to vscode april's update (v1.89.0). Downgrading vscode worked for me.

[DenisOstr]

Can you clone https://github.com/johnsoncodehk/volar-starter and reproduce the problem locally?

If yes, can you reproduce this problem for https://github.com/johnsoncodehk/volar-starter in GitHub Codespaces? If no, can you reproduce this problem for you project in GitHub Codespaces?

I tried and got the following result:

• Locally, it doesn't work either.
• I can’t check it in codespaces, but I tried it in VSCode Web (with only two extensions (Vue - Official and TypeScript IntelliSense for Web)), and it doesn’t work there either

[DenisOstr]

Same issue here. Seems related to vscode april's update (v1.89.0). Downgrading vscode worked for me.

I tried, but I'll try again

[DenisOstr]

@arielkern Which version did you install? I tried 1.88.1 but that didn't work either

[DenisOstr]

I tried VSCode version 1.88.1, it didn't work. I tried VSCode version 1.87.2, it didn't work. I uninstalled VSCode and everything related with it, installed both versions, it didn’t work

UPD: It seems to have been fixed, but only when I start typing does autocomplete work. If I just press ctrl + space, nothing is offered, not even what is in the component.

VSCode Version: v1.87.2 Vue - Official version: v1.8.27

[edarblanco]

Update VSCode version 1.89.1, it didn't work. Vue - Official version: v2.0.16

But, VSCode version 1.89.1 and Vue - Official version: v2.0.14 work

[DenisOstr]

What exactly works and how?

For me, with versions 1.87.2 and 1.8.27 (VSCode and Vue - Official), only autocomplete worked, and sometimes it doesn’t find certain things. Intellisense also doesn't work for me (when I'm just trying to call something without starting to type. Press CTRL + Space)

On version 1.89.1 I tried all versions of Vue - Official, none worked

[DenisOstr]

I've checked it now. It seems like autocomplete works on versions 1.89.1 and 2.0.16, but Intellisense doesn’t show me anything

[edarblanco]

I can exactly use autocomplete and so on, without any other changes, but I use Archlinux, I don't know if this could influence

[edarblanco]

Hello, a few minutes ago I updated to the latest version of Vue Official v2.0.17 with VS Code 1.89.1 and everything is fine.

[bosens-China]

Update to the latest version and set the tsconfig.json file to the following format

{
"CompilerOptions":{
"BaseUrl": "./",
"AllowJs": true,
"ResolveJsonModule": true,
//"Target": "ES2022",
"IsolatedModules": true,
"Strict": true,
"Paths":{
"~/*": [./*]
},
"OutDir": "./dist"
}
}

It seems that the target will cause an exception to occur

[fullmooooon]

delete Vscode plugin "vetur" use "Vue - official"

[okmkey45]

Hello everybody. I was having the same issue and none of the versions worked for me, not even downgrading the extension to 1.8.27

I found that there's a new feature in version 2 called Hybrid mode. I found this issue and it's kind of similar (I might be wrong). So, what I did was setting this new setting to typeScriptPluginOnly. Probably this is not best fix but at least, it helped me to enable IntelliSense again. So, I hope it can help you guys while this is properly fixed

[abubakriz]

I am on VSCode version v1.89.1 and Volar version v2.0.19

It doesn't seem to be able to autocomplete even basic things like auto importing ref and other components.

I don't know how I can help beyond saying what's happening to me, is there a way to get a debug log and send it here or something that will help the developers find the source of the issue?

[dalpii]

I'm experiencing something related to this, and I would like to provide some findings in hope that makes sense to maintainers.

I'm using Vue.JS + TypeScript, with default configs (no change regarding Vue/Volar). I'm also using Codespaces for development, so that's why I get this behavior pretty often.

Upon creation of a new Codespaces machine, after everything is installed, if I try to open a Vue file it seems everything is working, hover/IntelliSense on HTML is working fine, but once I try hover on a TypeScript variable I get nothing, and of course, not completions, etc.

Please take notice on this VSCode status:

I've enabled language server tracing, and once I hover a simple const I get this:

[Trace - 1:30:44 PM] Received response 'textDocument/hover - (22)' in 3ms.
No result returned.

I've noticed that restarting language server, or even just closing and reopening Codespaces didn't work either.

But what I found is that, once I restarted VSCode itself (quit and reopen the application), and load the same Codespaces, and open the same file, everything seems to magically works.

One thing I've noticed is that now I'm getting a new row with TS version on VSCode status:

I hope someone can reproduce this even on local codebases, and we get to the bottom of what's going on. Maybe something related to Hybrid Mode?

[ameryu716]

When will it be, this problem will resolved? This have always helped me, but as far as complementary functions are concerned, really, really, useless. ref,reactive,computed... various functions exist, but ,I haven't seen any of these codes auto import in the last two years. Until a few years ago, I was open to using the vetur extension as a transition period, but I think that time has passed. When will this extension work properly?

[leonward]

Hello everybody. I was having the same issue and none of the versions worked for me, not even downgrading the extension to 1.8.27

I found that there's a new feature in version 2 called Hybrid mode. I found this issue and it's kind of similar (I might be wrong). So, what I did was setting this new setting to typeScriptPluginOnly. Probably this is not best fix but at least, it helped me to enable IntelliSense again. So, I hope it can help you guys while this is properly fixed

This also allowed me to get suggestions functioning again, unsure of what else it could have broken. It's worth noting that I received a type error when setting this value away from auto, so I've set it to false in my settings.json

"vue.server.hybridMode": false

[KermanX]

Closing this issue because there seem to be multiple different problems that have similar behavior. Some of them were months ago and may no longer be applicable.

Possible fixes gathered from comments:

• Upgrade to the latest version
• Check VPN
• Check compilerOptions.target field in tsconfig.json
• Set hybrid mode to "typeScriptPluginOnly" or false in extension settings - However, this is only a temporary workaround. You may still need to open a new issue with the problem you're facing (with reproduction🫠).

@dalpii Thank you for providing this valuable information. I am not sure if this still happens in the latest version. If it still happens, please open a new issue. Thanks!

[dalpii]

I'm still having issues even after checking the possible fixes listed by @KermanX.

But I took some hours today to try a few more things. Although it was hard to replicate with a sample repository, I did these tests on a project we're working on, so quite few files.

My findings are somewhat strange, and I don't even know how to create a bug for this @KermanX, or even if it's a bug here, Codespaces, or something else. So as background, we use Codespaces here with default Microsoft images and configure to install some extensions, including this one.

So, if I create a new Codespace from scratch, wait for it to finish and load things, and try to open a .vue file, I get NO IntelliSense, no matter what I do (restart Vue server command from VSCode, etc.):

https://github.com/user-attachments/assets/a5251b9f-a8a4-43c4-8c1a-12621fadfac4

But again, if I create a new Codespace from scratch, but this time keep the "Extensions" tab open on VS Code, wait for all installation to finish, making sure to see the "time to load" appear on Vue extension (little ms), and then open the same .vue file, we can see that now it's showing on status bar that is "initializing JS/TS stuff" and IntelliSense works right away:

Sorry, this video is little bit longer: https://drive.google.com/file/d/1o5fKgwcxu46dbK32Ei7ZhrHhVXurJB8w/view?usp=share_link

I'm really not sure what's going on, but maybe something related to extension initialization?! I hope these findings help someone with more knowledge on how VS Code extension works.