-
-
Notifications
You must be signed in to change notification settings - Fork 112
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
nvm dont use default version in new terminals - VScode terminal #71
Comments
You may close this, after reboot, the vscode terminal started to persist the default node version |
not only VSCode terminal, also in iterm2 |
I am getting this problem. I am loading with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi!
I don't understand too well the zshrc config file, or PATH settings, so be patient with me :)
I just want to know why VScode dont use default version in new terminals
I use WSL2 on Windows, and its extension for VScode
I checked a lot of solutions, including:
nvm alias default stable
andnvm alias default node
, and it really updates my nvm, but dont change the version in new sessionsnvm deactivate
After that, I realized that my "Windows Terminal" (the new one) remembers the default node version in my WSL distro, but my VScode terminal dont
How is that possible?
Can anyone help me with this?
I dont really even know how to start looking for this problem..
(sry my bad english)
The text was updated successfully, but these errors were encountered: