Package Details: nvm 0.33.11-1

Git Clone URL: (read-only)
Package Base: nvm
Description: Node Version Manager - Simple bash script to manage multiple active node.js versions
Upstream URL:
Licenses: MIT
Submitter: tomwadley
Maintainer: tomwadley
Last Packager: tomwadley
Votes: 110
Popularity: 5.992132
First Submitted: 2015-03-14 21:57
Last Updated: 2018-04-25 20:38

Latest Comments

1 2 3 Next › Last »

tomwadley commented on 2018-08-25 19:19

@ferrantejake The post-install instructions explain that you have to source nvm into your shell before you can use it. This is unlike typical applications which install an executable into /usr/bin which you can just call out-of-the-box. This is the way nvm is designed and its a difficult problem to work around without making sacrifices that I don't think are appropriate to force on all users of the package. For example, I believe it would be possible for this package to install something in /etc to auto source nvm for all users, but that seems quite invasive to me. With some modifications to the way nvm works though, some sort of "system nvm" which doesn't require sourcing does seem possible, and it would be interesting to explore that one day, probably as a separate package.

For now, this package includes a handy script "/usr/share/nvm/" which you can source in your .bashrc to get nvm working.

ferrantejake commented on 2018-08-25 17:02

Seems to not be working out-of-the-box. I ran the following (from the nvm git repo) to get the package working in the command line:

export NVM_DIR="$HOME/.nvm" [ -s "$NVM_DIR/" ] && . "$NVM_DIR/" # This loads nvm

Would it be possible to get this added to the PKGBUILD script?

effeeffe commented on 2018-08-14 15:18

Now that package nodejs-fake does not exist anymore, what is the suggested way to go about this?

Twiki commented on 2018-08-11 18:11

@tomwadley You are right. Thanks! In the readme at Github, sourcing nvm is mentioned after the second "command -v nvm". I stopped after the first.

tomwadley commented on 2018-08-11 18:07

@Twiki you need to "source" nvm into your environment before you can run it. Look at the post-install instructions here that you may have missed

Twiki commented on 2018-08-11 17:43

Just installed, next to main Arch repo's already installed v10.8.0.

Result: nvm not found. command verify produces no output. nvm does exist.

[twiki@21stcentury 4.4.23 ~]# nvm run node --version

bash: nvm: command not found

[twiki@21stcentury 4.4.23 ~]# command -v nvm

[twiki@21stcentury 4.4.23 ~]# whereis nvm

nvm: /usr/share/nvm

[twiki@21stcentury 4.4.23 ~]#

-._. What went wrong?

FranklinYu commented on 2018-07-17 19:53

Note that for may not work for every Zsh user, such as one who wants separate path for .zcompdump files, because option is hardcoded in bash_completion. I fell back to zsh-completions.

ljharb commented on 2018-06-29 01:32

Hi Fandekasp - do you have a "prefix" line in your ~/.npmrc, perhaps? If so, remove it.

If that doesn't work or apply, please file a new issue on the nvm github repo. Thanks!

Fandekasp commented on 2018-06-29 01:15

Recently, I'm getting the following message everytime I open a shell

nvm is not compatible with the npm config "prefix" option: currently set to "" Run npm config delete prefix or nvm use --delete-prefix v10.5.0 --silent to unset it.

Uninstalling and re-installing nvm didn't fix the issue. Running the 2 commands suggested doesn't change anything either

tomwadley commented on 2018-01-29 13:57

@Depado This package doesn't create that file. I think that file is created by the official if you tell it to enable nvm for all users on the machine (an idea that might be worth looking into for this package actually). I guess you should follow the official uninstall instructions if you've used the official script.