language-tools
language-tools copied to clipboard
vuejs
VSCode extension loses all highlighting, auto imports, intellisense, etc.
I seem to have lost use of essentially all the functionality I care about in the VSCode extension. I have no highlighting, auto-imported components, etc. As a minimal reproduction, I created a new Vuetify project using their generator. For this, I ran pnpm create vuetify with the default options and pnpm as my package manager
Running the Vue: Restart Vue and TS servers command in my command palette reports the following in the Output tab:
[Error - 2:19:40 PM] Server process exited with code 0.
[Vue Named Pipe Client] No server found for c:/temp/vue/vuetify-project/src/App.vue
Environment: Version: 1.88.1 (user setup) Commit: e170252f762678dec6ca2cc69aba1570769a5d39 Date: 2024-04-10T17:41:02.734Z Electron: 28.2.8 ElectronBuildId: 27744544 Chromium: 120.0.6099.291 Node.js: 18.18.2 V8: 12.0.267.19-electron.0 OS: Windows_NT x64 10.0.22621
Try to roll back to version v1.8.27. If there is unocss plug-in, it will be disabled. It is running normally now.
Hey guys, my problem was on vscode 1.88. Both Microsoft VSCode and VSCodium.
The solution for me was rollback the VSCodium version to 1.87, Microsoft VSCode don't let me rollback the version on ubuntu.
Let me know if it works.
Our team resolved this by rolling back Vue plugin - official to v2.0.6
This issue has been very disruptive, rolling back Vue - Official plugin to v2.0.6 as per @wmurphyrd fixed it for me as well.
FWIW, "Vue Language Server" output looks like this for me:
[Vue Named Pipe Client] No server found for c:/Users/astamant/Source/Repos/project/project-vue/src/modules/Customer/CustomerHome.vue
Using VS Code, I have the same issue but do not even get any output from "Vue Language Server". Rolling back to 2.0.6 works.
I'm getting [Vue Named Pipe Client] No server found for ..... and [Vue Named Pipe Client] Timeout. Rollback to 2.0.6 is not working for me.
Vue plugin 2.0.14 vue-tsc 2.0.14
Edit: fixed it by deleting all node_modules folders (mono repo), package-lock.json and run npm install...
Just found this my side, easily reproducable by creating a new Vuetify project, opening VSCode into the solution, then hovering over any vuetify control
@wmurphyrd How'd you roll back? My VSCode shows no previous versions
Edit: Here's a tutorial https://github.com/microsoft/vscode/issues/12764#issuecomment-442370545
code --install-extension [email protected]
Double edit: Downgrading doesnt work
Just found this my side, easily reproducable by creating a new Vuetify project, opening VSCode into the solution, then hovering over any vuetify control
@wmurphyrd How'd you roll back? My VSCode shows no previous versions
Edit: Here's a tutorial microsoft/vscode#12764 (comment)
code --install-extension [email protected]Double edit: Downgrading doesnt work
Can confirm this, I just created a new Vuetify project using Vuetify;s CLI and it's not working, but Nuxt projects do work without problems (imports, suggestions...)
Just found this my side, easily reproducable by creating a new Vuetify project, opening VSCode into the solution, then hovering over any vuetify control
@wmurphyrd How'd you roll back? My VSCode shows no previous versions
Edit: Here's a tutorial microsoft/vscode#12764 (comment)
code --install-extension [email protected]Double edit: Downgrading doesnt work
The same situation, but when I rolled back to version v1.8.27, it seemed to get a little better.
Could identify functions that were not implemented. In v2.0.6, the extension did not remind that the function did not exist. But still cannot recognize vuetify controls:
------edit------
I've noticed this reply: https://github.com/vuejs/language-tools/issues/4421#issuecomment-2139294691
I made changes to the tsconfig.json file based on the content in this reply, and now everything is working fine.
And it also applies to the v2.0.19 extension.
True, since we are using ts plugins in v2, you must explicitly include vue files in your tsconfig.
I found that the plugin only started to work again when removing the **.vue files from the "include" section of the TS config. Resulting in other errors being reported by vue-tsc, but I haven't investigated these issues closely now. Seemed to be only related to usages of arrow functions in the template section where the types couldn't be correctly derived anymore.
Hey there, as there have been many fixes in the last 2.x versions: If you're still encountering issues, please provide a minimal reproduction. Otherwise kindly close this one, thanks!
Vue - Official just didn't work before and now it doesn't work with the VS Code version 1.93.1. The version here does not matter at all. This extension does not work with any version. I just use Vetur which at least shows errors.
