Package Details: nvm 0.37.2-1

Git Clone URL: (read-only, click to copy)
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: 163
Popularity: 2.78
First Submitted: 2015-03-14 21:57
Last Updated: 2020-11-28 17:09

Dependencies (1)

Required by (24)

Sources (3)

Pinned Comments

tomwadley commented on 2020-09-04 22:14

Due to the way nvm is designed, you have to source it before you can use it:

source /usr/share/nvm/

You will probably want that in your shell startup file, e.g.:

echo 'source /usr/share/nvm/' >> ~/.bashrc

See nvm.install or the upstream README for more details.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

tomwadley commented on 2019-03-25 13:37

Thanks for the tip @jamespharvey20. I wasn't aware of SRCDEST. Fixed.

jamespharvey20 commented on 2019-03-25 09:06

Downloaded source filenames must be unique, for those who set SRCDEST in /etc/makepkg.conf. See

Please add something like this to the beginning of source:


tomwadley commented on 2019-03-17 17:53

@joshsteele21 You shouldn't have to change any permissions or use sudo. And you're sourcing (as opposed to executing) right? Have you previously tried to install nvm the "official" way from their readme? There could be some sort of conflict going on there.

joshsteele21 commented on 2019-03-08 02:26

Installation and running the script works fine, but running nvm install node does not work because of permission denied errors. Using sudo does not recognize the nvm command (sudo: nvm: command not found)

EDIT: Do I need to manually change the permissions on /usr/share/nvm ?

FranklinYu commented on 2019-02-10 16:55

@bobpaul Actually NVM is not designed to be used in script, IIUC. Please notify those project owners that nvm-exec is the correct tool for non-interactive use. Or is there any example for us to have a look?

EDIT: please forgive my innocence and ignore the comment above. Official suggestion is to use nvm exec which expects to be in $NVM_DIR.

tomwadley commented on 2019-02-07 22:50

@bobpaul thanks for the suggestion. I've made this change over on nvm-git [0]. Can you take a look and see if that works for you? If I don't hear any complaints, I'll push the same change to this package in a day or two.


EDIT: I've pushed the change here too.

bobpaul commented on 2019-02-06 19:24

@tomwardley I've encountered projects that use nvm inside their own bash script. Since bash scripts don't inherit bash functions from the parent shell, these projects all expect to see inside $NVM_DIR. This is solved with ln -s /usr/share/nvm/ $NVM_DIR/. Can you add that to the same script that copies nvm-exec?

FranklinYu commented on 2018-12-29 02:02

@Codex0 After installing, you should see your package manager prompting you to do so. If not, you should get a better package manager.

About why you need to do so, package maintainer has explained it on August 25th, 2018. Please find the corresponding comment.

Codex0 commented on 2018-12-28 14:50

Found that despite installing this I still had to manually execute:

echo 'source /usr/share/nvm/' >> ~/.bashrc
exec $SHELL

tomwadley commented on 2018-11-04 21:50

@hutliver Sorry to hear it. In that case, it's not a package issue. I'd suggest seeking help from upstream. Read their readme to make sure you haven't missed something. Otherwise, they're pretty responsive to Github issues.