-
Notifications
You must be signed in to change notification settings - Fork 12
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
doesn't work in remote with nvm #12
Comments
+1 |
2 similar comments
+1 |
+1 |
I got it going based on this answer: You need to make sure (if your using a .bashrc) that the NVM initialization is above the following in your .bashrc file. # If not running interactively, don't do anything
case $- in
*i*) ;;
*) return;;
esac |
@Yvem In my opinion this is more of an environment issue than a shipit-npm issue, is delusive's answer satisfactory for you? I would agree with you if there weren't such a myriad of ways to install node, putting an option to cover all of them might be a heck of a ongoing task. |
+1 |
should have an option to run
nvm use default
before running npmusing shipit-nvm doesn't help.
The text was updated successfully, but these errors were encountered: