-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
tsserver won't start - WSL? #88388
Comments
Where is your code stored? Somewhere besides the |
Yes sir. It's on a separate drive entirely |
Duplicate of microsoft/TypeScript#35512 To workaround this, upgrade your workspace to use |
@mjbvz it turns out I actually don't have these on the |
Are you using the vscode wsl-remote extension? If not, can you please explain how you are opening the folder |
Yes, using |
Opening new issue to avoid confusion. |
Version: 1.41.1 (user setup)
Commit: 26076a4
Date: 2019-12-18T14:58:56.166Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.19041
Steps to Reproduce:
After opening and watching "Initializing js/ts server...". I verbose logging shows a whole mess of stuff, happy to put it all here if needed.
Some that stick out:
[Trace - 19:30:30.496] Response received: updateOpen (2). Request took 137986 ms. Success: true
This took over 2 minutes.
[Trace - 19:30:31.120] Response received: getSupportedCodeFixes (3). Request took 138609 ms. Success: true
This took another 2 minutes.
[Trace - 19:30:37.291] Response received: configure (4). Request took 144779 ms. Success: true
Again.
Then it just kind of hangs. I noticed when I try to force some intellisense (with ctrl+space) I see these errors:
I tried reinstalling VS Code. I tried Insiders. All my extensions (except for WSL Remote) are disabled. Happy to help or get more information if needed.
The text was updated successfully, but these errors were encountered: