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
Node version not detected correctly on WSL2 #2522
Comments
That sounds like a Code ( |
cc microsoft/vscode-remote-release#385 Not sure what's going on here, we probably need to either change our installation instructions, or to provide a better error message. The relevant code is here: I personally won't be able to look into this anytime soon |
I see now I just missed the existing instructions for installing on vscode on a remote host. A relevant error message for someone using the wrong install method would be great though. |
3389: Note vscode remote limitation when client install fails r=matklad a=not-much-io Just adding a note about the limitation referenced in #2522 Considered checking if this message is relevant in the context (is this remote?) but decided against it because of return on investment - seeing how fast vscode iterates this limitation might just disappear in the near future. Also checked if there is a way to already do this which lead me to leaving a specifing question at microsoft/vscode-remote-release#385 Co-authored-by: nmio <kristo.koert@gmail.com>
Presumably fixed in #3389. |
I'm trying to install rust analyzer vscode extension from WSL2 (Ubuntu 18.04), but I get an error message about needing node > 10.x.
however I have node v12.13.1 in my Windows path and v13.3.0 in WSL.
Full output;
The text was updated successfully, but these errors were encountered: