Some Problems with VSCode Extension #146
-
Hi, I tried to make this example myself: https://github.com/volarjs/vscode-typescript-web However, I get the following errors: import {
createConnection,
startLanguageServer, // Module '"@volar/language-server/browser"' has no exported member 'startLanguageServer'.
LanguageServerPlugin, // '"@volar/language-server/browser"' has no exported member named 'LanguageServerPlugin'. Did you mean 'LanguagePlugin'?
InitializationOptions
} from "@volar/language-server/browser";
import createTsService from "volar-service-typescript";
config.services ??= {};
config.services.typescript = createTsService(); // This expression is not callable.
// Type 'typeof import("/home/cemalgnlts/jside/node_modules/volar-service-typescript/index")' has no call signatures. I wonder if the APIs have changed. What their current usage has been replaced with. |
Beta Was this translation helpful? Give feedback.
Answered by
johnsoncodehk
Feb 29, 2024
Replies: 1 comment 1 reply
-
Yes, the API has changed. You can refer to this migration PR. Since the Vue language tools it depends on have not been upgraded to Volar v2, and the @volar/cdn used for ATA has been removed, it cannot be upgraded to Volar v2 for the time being. |
Beta Was this translation helpful? Give feedback.
1 reply
Answer selected by
cemalgnlts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, the API has changed. You can refer to this migration PR. Since the Vue language tools it depends on have not been upgraded to Volar v2, and the @volar/cdn used for ATA has been removed, it cannot be upgraded to Volar v2 for the time being.
volarjs/vscode-typescript-web#6