Language server critical regression from 2.0.5 to 2.0.6

[aentwist]

Actual

Hi, I am facing some critical language server issue on 2.0.6. It was a very mysterious issue, so after seeing 2.0.6 is a new release I decided to regress to 2.0.5, which does not have this problem as it turns out.

I'm not sure what information is needed, if any, but I am willing to provide the required details.

Expected

Language server works; installing 2.0.5 and reloading does this

Environment

Volar (vue.volar)

2.0.6

VSCode

Version: 1.87.1 (user setup)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:36.258Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.22631

Remote

WSL Deb 12

[aentwist]

My colleagues do not seem to be having this issue but it is consistent for me. Feedback appreciated

[NothingEverWorks]

Same issue for me in Nuxt. Vue highlighting is not working in 2.0.6.

The fix is to revert back to Vue - Official 2.0.5

[pm0u]

Just upgraded to 2.0.6 this morning on a vue/webpack project and am not seeing this issue.

I have a separate vue/nuxt project that seems to have lost all typing for any imported components or nuxt builtins though. HTML elements seem fine.

    "nuxt": "^3.10.3",
    "vue": "^3.4.19",

Seem to have lost all intellisense for node_modules

Downgrading to 2.0.5 did not resolve.

[aentwist]

Not Nuxt related I'm on Vue / Vite (Rollup)

[pm0u]

Got it - in my case it was due to #3942 - having the styled-components extension installed.

disabling styled-components.vscode-styled-components resolved, does not seem to be Vue extension version related. I was able to use v2.0.6 once I disabled. Difference between the 2 contexts for me was due to the extension already being disabled via a workspace extensions.json that I did not account for.

[so1ve]

Does it work now? Should be fixed by #4119