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 »

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.

Depado commented on 2018-01-29 10:00

Just a heads up, when uninstalling the package, /etc/profile.d/ isn't deleted. This caused my X session to fail on startup. (I have no idea if that's just me or if that happened to someone else)

darkbasic commented on 2018-01-23 09:59

@givemeurhats The nodejs-fake you were talking about does not exist...

givemeurhats commented on 2018-01-19 01:36

Check out which takes care so packages like npm don't install nodejs as their dependency, keeping nvm the only source of nodejs on the system.

ljharb commented on 2017-06-01 22:05

@tomwadley Makes sense. I still think nvm itself should be stored in the home directory, but as long as it works, that's fine.

The reality, of course, is that without a second factor on a separate communications channel, the system package manager isn't any more secure than curl | sh :-) no need to get into the "security theater" argument here, of course.

My hope is that this AUR approach won't be like every other attempt before it to package nvm via an unsupported method; but that instead, this one will actually *work* and not cause bugs. So far, there's been few complaints, so congrats!

tomwadley commented on 2017-06-01 18:28

Hi @ljharb,

Firstly, thanks for dropping in and for all of your work on nvm. I (and I'm sure everyone using this package) really appreciates everything you're doing.

To answer your question, if the user follows the instructions, NVM_DIR *is* actually set to $HOME/.nvm. It's only that nvm itself is put in /usr/share.

To elaborate a little more, this package is for people, like me, who prefer to have all of their installed software managed by their system package manager rather than installing things with a curl-pipe-bash. A lot of people also prefer not to have a script (such as your making changes directly to files in their home directory. The philosophy behind doesn't sit well with me and I wanted to be able to install nvm without using it.

Of course, the fundamental design of nvm is that its a sourced shell function which makes it difficult to package as though it were a normal system executable. It is unfortunate that even with this AUR package, users must still edit their personal .bashrc files. But if this is necessary, I believe Arch users would prefer to do that by hand.

ljharb commented on 2017-06-01 06:40

Hi, / maintainer here.

@lwin please file an issue on the upstream repo; slowness is generally due to `npm config get prefix` being slow.

@lacrymology you're using an old/never worked properly `nvm` that was incorrectly installed from `npm`. `npm uninstall -g nvm`, and then please reinstall it properly (from the install script, or this AUR package).

@rulatir nvm is a sourced shell function - there is no binary, no executable. When you source ``, you'll get an `nvm` function available in your shell.

@tomwadley is there a particular reason that this installs $NVM_DIR to a non-user-specific place? nvm is per-user, and should not be shared across user accounts.

In general to everyone, please start by filing an issue on the git repo directly - - and please call out you're installing it via this AUR package. If it's a packaging problem, I'll point you back here. Thanks!

tomwadley commented on 2017-01-18 23:11

@lwin I believe this is an upstream issue and not related to the packaging although I'd be happy to be proven wrong. It's also slow for me. There are various issues on github complaining about slow loading. Let me know if you figure anything out.