Default NVM_DIR variable not portable between OSes

[lexrj]

Because it is adding variables to .bashrc, it should be safe to assume the $HOME variable is set. Would it be possible to have the line that is appended to .bashrc be export NVM_DIR="$HOME/.nvm" to afford portability of profiles between systems?

Noticed this when copying my .bashrc from linux to OS X and having the install script fail because it couldn't install the the NVM_DIR specified by my linux .bashrc.

[ljharb]

That does seem like a reasonable change.

[DesignByOnyx]

I am experiencing this same issue. I share my bash profile across several machines. Updating to use NVM_DIR="$HOME/.nvm" allowed me to keep working. Also worth noting that rvm uses $HOME in their scripts.

[ljharb]

@DesignByOnyx note that you're welcome to do this manually after installing nvm, it's only on the first install that this request would change anything.

[DesignByOnyx]

Yeah, I saw that in the shell script -> you don't touch the profile if NVM_DIR already exists. For my situation, I installed nvm on Machine A weeks ago, moved to Machine B, installed nvm, and got a warning that the directory /Users/machine-a-user/ does not exist. The one time change was easy, but I wanted to support the use of $HOME instead.