nvm is not compatible with the npm config "prefix" option when /home is a symlink

[jeffrson]

nvm worked for me, until I needed to move /home to another partition and set /home a symlink to the new location.

I think there is not much need for any details. The cause is probably node's behaviour with symlinks. So you may have to rethink about the prefix behaviour in such case.

Following the error message node cannot be used at all:

$ nvm install 14.10.1
v14.10.1 is already installed.
nvm is not compatible with the npm config "prefix" option: currently set to "/data/home/user/.nvm/versions/node/v14.10.1"
Run `nvm use --delete-prefix v14.10.1` to unset it.
Creating default alias: default -> 14.10.1 (-> v14.10.1)
$ node -v
-bash: node: Command not found

/home is a symlink to /data/home.

[ljharb]

Indeed, this is a duplicate of #617. nvm doesn't support your home dir or nvm dir being a symlink.

Could you hard link /home instead of symlinking it? That would likely cause a lot fewer problems with various tools.

[jeffrson]

Oops, sorry - haven't found this existing report, when searching for "prefix" messages.

No, directories cannot be hard linked. I put /home back and symlinked another larger directory. So nvm works again, but unfortunately this is not quite a solution.

Closing anyway in favor of the older issue.

Thanks!