Takeover mode cannot find TypeScript at path defined in settings.json anymore

[Anoesj]

Ever since I updated to vue-tsc 1.4.x, it seems like Volar cannot find my TypeScript lib anymore in Takeover mode. I defined this in .vscode/settings.json, because my folder structure is a little different (no node_modules in the root directory):

{
  "typescript.tsdk": "SomeDir/AnotherDir/node_modules/typescript/lib"
}

I get x.x.x (takover) in the bottom bar in VSCode and when clicked, it shows:

Interestingly, selecting VSCode's version of TS doesn't work anymore either, it shows notifications like "Vue Semantic Server client: couldn't create connection to server" outputs this to the Vue Semantic Server output tab:

[Info  - 11:40:58 PM] Connection to server got closed. Server will restart.
true
[Error - 11:40:58 PM] Server initialization failed.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in undefined
  Code: -32603 
[Error - 11:40:58 PM] Vue Semantic Server client: couldn't create connection to server.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in undefined
  Code: -32603 
[Error - 11:40:58 PM] Restarting server failed
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in undefined
  Code: -32603 
[Error - 11:41:00 PM] The Vue Semantic Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

Any chance the vue-tsc update has anything to do with this?

[johnsoncodehk]

Can you try relative path?

{
  "typescript.tsdk": "./SomeDir/AnotherDir/node_modules/typescript/lib"
}

[wenyongda]

I have the same problem.
{
"typescript.tsdk": "node_modules/typescript/lib"
}

[Error - 09:18:39] Restarting server failed
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in undefined
  Code: -32603 
[Error - 09:18:42] The Vue Semantic Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
[Error - 09:18:54] Server initialization failed.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in undefined
  Code: -32603 
[Error - 09:18:54] Vue Semantic Server client: couldn't create connection to server.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in undefined
  Code: -32603 
[Error - 09:18:56] The Vue Semantic Server server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.

[Tanimodori]

1.4.0 breaks tsdk for me too. It cannot loads correct in my rush monorepo. The symptoms are identical to those reported above. Tried to set typescript.tsdk to the following values but none of them works.

• common/temp/node_modules/typescript/lib
• ./common/temp/node_modules/typescript/lib
• C:/path/to/project/common/temp/node_modules/typescript/lib (absolute path)

Rolling back to 1.3.x won't solve this problem for me (tried 1.3.19, 1.3.16).

[johnsoncodehk]

Please try v1.4.1.

[wenyongda]

It's normal.Thank you very much

[Anoesj]

I can confirm it's working again, thanks for the super fast response @johnsoncodehk ❤️

[Tanimodori]

It works for me in 1.4.1. Thanks for the quick fix! ❤️

[0biWanKenobi]

Sorry but it's still broken for me, I have x.x.x (takeover) in the bottom toolbar and this error when opening the TS version picker:

I am on Windows, vue-tsc version 0.31.4

[edit]: rolling back to Volar 1.2.0 solved it. Apparently Volar 1.4.1 is no longer compatible with older versions of vue-tsc?

[rajeshtva]

Apparently broken on my system as well..
volar version: 1.4.2

Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /home/rex/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib

[Error - 12:04:51] Server initialization failed.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /home/rex/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib
  Code: -32603 
[Error - 12:04:51] Vue Semantic Server client: couldn't create connection to server.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /home/rex/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib
  Code: -32603 

[Eyre-S]

Apparently broken on my system as well.. volar version: 1.4.2

Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /home/rex/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib

[Error - 12:04:51] Server initialization failed.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /home/rex/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib
  Code: -32603 
[Error - 12:04:51] Vue Semantic Server client: couldn't create connection to server.
  Message: Request initialize failed with message: Can't find typescript.js or tsserverlibrary.js in /home/rex/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib
  Code: -32603 

There's the same problem on my computer.

seems volar trying to find typescript lib on ~/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/extensions/node_modules/typescript/lib but the actuall file location is ~/.vscode/extensions/ms-vscode.vscode-typescript-next-5.1.20230421/node_modules/typescript/lib.

I solved this problem by rolling back my volar version from 1.4.2 to 1.4.1.

[H0nGzA1]

for me select this it's working

[yingpwu]

Change the extension of Vue Language Features (Volar) and TypeScript Vue Plugin (Volar) from version 1.4.2 to 1.4.1 will backto work ,
This problem confused me 2 hours ,mygod......
I turn off the autoupdate now

[johnsoncodehk]

The correct issue is #2663, it should be fixed and released in v1.4.3.