-
-
Notifications
You must be signed in to change notification settings - Fork 399
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
Receiving error "Vue Semantic Server client: couldn't create connection to server." since upgrading to 1.0.0 #1942
Comments
It seems a same problem: #1880 (comment) But I don't know how it resolve, can you try reinstall extension and restart vscode? |
I've just tried Details
I suppose it has to do with (note that it tries to use typescript v4.8.4) EDIT: Also tried with |
I have tried re-installing it and restarting vscode and even restarting the machine. My colleague and I have the same setup and his is working with the latest extendion so I enabled the verbose logging you mentioned on the other thread and compared it between the two environments, the only difference is in the typescript initializationOptions where the tsdk path on mine is pointing at the workspace and his is posing at the global install. Working
Failing
|
@rchl please try update "initializationOptions": {
- "documentFeatures": {
- "documentColor": true,
- "documentFormatting": {
- "defaultPrintWidth": 90
- },
- "documentSymbol": true,
- "foldingRange": true,
- "linkedEditingRange": false,
- "selectionRange": true
- },
- "languageFeatures": {
- "callHierarchy": false,
- "codeAction": true,
- "codeLens": {
- "showReferencesNotification": true
- },
- "completion": {
- "defaultAttrNameCase": "kebabCase",
- "defaultTagNameCase": "both",
- "getDocumentNameCasesRequest": false,
- "getDocumentSelectionRequest": false,
- "ignoreTriggerCharacters": ""
- },
- "definition": true,
- "diagnostics": true,
- "documentHighlight": true,
- "documentLink": true,
- "hover": true,
- "implementation": true,
- "inlayHints": true,
- "references": true,
- "rename": true,
- "renameFileRefactoring": false,
- "schemaRequestService": false,
- "semanticTokens": true,
- "signatureHelp": true,
- "typeDefinition": true,
- "workspaceSymbol": true
- },
+ "ignoreTriggerCharacters": ""
"textDocumentSync": 2,
"typescript": {
- "serverPath": "/Users/rafal/Library/Caches/Sublime Text/Package Storage/LSP-volar/16.15.0/server/node_modules/typescript/lib/tsserverlibrary.js"
+ "tsdk": "/Users/rafal/Library/Caches/Sublime Text/Package Storage/LSP-volar/16.15.0/server/node_modules/typescript/lib"
}
} |
In my case above it was about the path pointing to a file rather than the Also I guess make sure that the directory and files within it do exist. |
@alan-strickland-red I just found a way to reproduce it under specific conditions, please wait for v1.0.1. Reproduce steps:
|
@johnsoncodehk Thank you. |
@alan-strickland-red You can try to change to VSCode Version tsdk in status bar to avoid this problem for now. |
@johnsoncodehk That's fixed it. I changed to "Use Workspace Version 4.8.4", note of interest switching back to "Use VC Code's Version" also works. |
+1 |
I installed the previous version of fly and it worked for me. as a temporary solution. |
Sorry to bother you all, but this problem has prevented me from using vscode to write vue projects, and using the above method has not solved the error and plugin failure. |
+1 |
Same problem, downgrading the plugin worked |
Just started showing up for me aswell. |
May I know which version you have downgraded to? |
I downgraded to version 1.4.0 ,it can run normally |
Same problem, I think this must have happened with an update as it only started yesterday. When I check the output I see:
So what this tells me is that this problem has something to do with the Microsoft official typescript extension. What to do?, Here's some solution that'll work. Open your extension list and disable this extension for your workspace. Alternatively, install a different version of the extension. However, for me, it only worked after disabling the extension. I guess there might be some incompatibility with Volar and vscode-typescript-next recent changes. |
Please update your extension to v1.4.3 or later, and please don't reply on an obsolete issue. |
@johnsoncodehk Thanks, I see this is resolved in |
👍 |
I mean this issue (#1942) is obsolete, it has nothing to do with the problem with the new version. You should be able to see the prompt message from github. |
I agree, unfortunately, it happened to be the only related issue with the most engagement and most recent comment. Thanks again. |
Hi,
Since VSC upgraded to Volar to 1.0.0 automatically this afternoon I am getting errors when loading .vue files.
The output window for the Vue Semantic Server shows the following errors repeatedly:
The output window for the Vue Syntactic Server shows the following errors repeatedly:
I have downgraded to Volar 0.4 and that has resolved the issue for the time being.
The text was updated successfully, but these errors were encountered: