You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
node version installed before nvm -> no
i tried nvm alias default stable and nvm alias default node, and it really updates my nvm, but dont change the version in new sessions
i tried nvm 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:
I am getting this problem. I am loading with plugins=(git zsh-autosuggestions zsh-nvm) in my .zshrc file, and my new window panes in tmux, and new tabs in iterm2, always default to node 14, while I want node 16. I have tried all sorts of combinations like nvm use default 16. Nothing works.
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: