Arch Linux User Repository

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

source /usr/share/nvm/init-nvm.sh

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

echo 'source /usr/share/nvm/init-nvm.sh' >> ~/.bashrc

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

@tukusejssirs as I replied to @meijin, this package doesn't create those files. In fact, the entire purpose of nvm is to not pollute your system node installation. With nvm you install a local version of node and npm, with a local node_modules for "globally" installed packages.

If for example I install a package globally:

nvm use 16 # Now using node v16.14.0
npm install -g pm2

It will install into my local node's node_modules. For me that is: ~/.nvm/versions/node/v16.14.0/lib/node_modules/pm2/. nvm also put this on my PATH so I have access to the global pm2 binary (and for that matter the npm and node binaries themselves): ~/.nvm/versions/node/v16.14.0/bin.

I experienced same conflict as @meijin has described in his comment, at least twice in the past month (I think it occurred every time npm package installed via pacman was updated).

The error from pacman -S npm (run via yay -S npm) I had today was:

error: failed to commit transaction (conflicting files)
npm: /usr/lib/node_modules/npm/lib/package-url-cmd.js exists in filesystem
npm: /usr/lib/node_modules/npm/lib/utils/format-search-stream.js exists in filesystem
Errors occurred, no packages were upgraded.
 -> error installing repo packages

I worked this issue around simply renaming /usr/lib/node_modules, installing npm and restoring globally installed NPM packages:

# Move old global `node_modules`
sudo mv /usr/lib/node_modules{,.bak}

# Reinstall system `npm`
yay -S npm

# Remove packages installed by `npm` system package
sudo rm -rf /usr/lib/node_modules.bak/{node-gyp,nopt,npm}

# Move previously globally installed NPM packages into newly installed global `node_modules`
sudo mv /usr/lib/node_modules.bak/* /usr/lib/node_modules

# Remove old global `node_modules`
sudo rmdir /usr/lib/node_modules.bak

I hope this issue will be solved, however, I have no idea why it happens in the first place.

Solution to issue below:

The package is fine. My config was the problem.

I'm using zsh as my shell and had the line source /usr/share/nvm/init-nvm.sh in my .zshenv. Moving it to .zshrc fixed it.

Looks like my distro sources .zshenv on every keybinding I press. I don't know...

Issue

Beginner in arch here. I installed the EndeavorOS bspwm (community) edition and it works perfectly until I install this package.

This is how I installed it:

yay -S --noconfirm nvm
source /usr/share/nvm/init-nvm.sh
nvm install node

and all of a sudden all of my keybindings take 1-2 seconds to register, as opposed to instantly.

I went so far as to reinstall the distro and install each package I use and reboot the system (I know it's overkill) until I found what was slowing it down.

After finding out, removing this package with yay -Rusn nvm "fixed" the problem.

@meijin this package doesn't create those files. nvm is for installing a local (per-user) version of node. The local version you install won't conflict with the system version.

maybe it should be conflict with node/npm packages? or provide them? because otherwise when something is trying to install node/npm as dep:

error: failed to commit transaction (conflicting files)
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-access.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-adduser.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-audit.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-bin.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-bugs.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-cache.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-ci.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-completion.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-config.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-dedupe.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-deprecate.md exists in filesystem
npm: /usr/lib/node_modules/npm/docs/content/commands/npm-dist-tag.md exists in filesystem
...

No problem @alexnortung, all good :)

@tomwadley Yes my bad, I feel pretty dump for commenting on the wrong package.

@alexnortung this package does not install node. This package is for nvm, which is a shell script you can use to install node. Did you mean to comment on the session-desktop package?

Installing does not work at the moment. I get an error:

error session-desktop@1.6.3: The engine "node" is incompatible with this module. Expected version "^10.19.0". Got "10.13.0"
error Found incompatible module.

It seems like the PKGBUILD is installing the 10.13.0 version of node. But for some reason it expects 10.19.0.

@tomwadley I can confirm that's working now. Thanks for the help!

@tomwadley thank you :) i can confirm, that it does work now

Thanks for the report @protolomeo and sorry for the delay @garlonion. I reproduced the issue in a chroot. It looks like there were some files in the zip which had characters in the filenames that were causing issues with bsdtar depending on your locale.

I switched to the tarball which I think has fixed the issue. Please let me know. Not sure why I wasn't using the tarball in the first place. I guess there was only a zip available when I created the package.

@garlonion I have the same exact issue.

locale -a
C
POSIX
it_IT
it_IT.iso88591
it_IT.utf8
italian

@tomwadley i already tried using no aur helper before i commentet here. And the output from using bsdtar directly is the same:

❯ bsdtar -xf v0.38.0.zip
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename ... skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename ... skipping.
bsdtar: Error exit delayed from previous errors.

@garionion can you try downloading the zip file manually and extracting it with bsdtar? i.e.

$ wget https://github.com/nvm-sh/nvm/archive/refs/tags/v0.38.0.zip
$ bsdtar -xf v0.38.0.zip

If that works, the next thing I'd try is to build this package without using any AUR helper (download snapshot, run makepkg).

hi, with 0.38.0-1 i get "Failed to extract nvm-0.38.0.zip":

==> Extracting sources...
  -> Extracting nvm-0.38.0.zip with bsdtar
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename ... skipping.
bsdtar: Pathname cannot be converted from UTF-8 to current locale.
bsdtar: Archive entry has empty or unreadable filename ... skipping.
bsdtar: Error exit delayed from previous errors.
==> ERROR: Failed to extract nvm-0.38.0.zip
    Aborting...

My locale is:

❯ locale -a
C
C.utf8
POSIX
de_DE
de_DE.iso88591
de_DE.iso885915@euro
de_DE.utf8
de_DE@euro
deutsch
en_US.utf8
german

Do you have any ideas?

@CliffJumper I can't reproduce that. I downloaded it manually and double checked - seems fine to me. Is it still happening?

For nvm 0.38.0 I'm getting a mismatch in the sha256 sum for the zip file

@joshsteele21 I found out that the cause was that I used a GUI tool to change the LC_TIME, but the locale I changed it to wasn't installed. I guess that's a bug in KDE.

Changing it to a locale that was actually supported has solved the issue.

@foxite I have a similar issue, it happens every once in a while after an update. Apparently the issue has to do with glibc, at least in my case. There are files missing in /usr/share/i18n/locales

see https://unix.stackexchange.com/questions/604134/how-to-fix-missing-locale-files-on-manjaro/

@foxite presumably there is something wrong with your locale config. Take a look at the Locale wiki page.

Edit: For some reason I had assumed that sourcing init-nvm.sh was causing the error, but it's more likely that init-nvm.sh is encountering an error.

Adding this line to .bashrc as instructed:

source /usr/share/nvm/init-nvm.sh

Causes the following message to appear when I open a terminal:

manpath: can't set the locale; make sure $LC_* and $LANG are correct

Removing the line causes the message to go away, though obviously I can't use nvm without it. I suspect that this is related to the inexplicable locale errors I have been getting in various other command line tools. Upon inspection, there seems to be nothing wrong with $LANG or my $LC_* variables; they are the same with or without init-nvm.

Any ideas what is causing this problem or how to fix it? It is pretty annoying, but seems harmless.

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

source /usr/share/nvm/init-nvm.sh

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

echo 'source /usr/share/nvm/init-nvm.sh' >> ~/.bashrc

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

How do I use nvm these days? In the past, this package exposed nvm command I could freely use.

@FranklinYu The reason I kept them separate is because install-nvm-exec feel a little more "controversial" to me. I can imagine some people explicitly not wanting install-nvm-exec to run as it modifies your home directory... (not much mind you - it just creates ~/.nvm and puts some symlinks there)

But you're right that if users want to avoid install-nvm-exec they would also be avoiding init-nvm.sh as well.... so maybe keeping them separate is silly.

But the need to do that really highlights the way in which nvm was not designed to be packaged via a system package manager like pacman. The "official" way to install it is via their install.sh script which makes way more drastic changes to your home directory! (edits ~/.bashrc etc.)

Do you think it makes sense to merge install-nvm-exec into init-nvm.sh? Both scripts are very short.

Thanks for the heads-up @donsmith - I've updated the url.

@tomwadley, just a heads-up for your next update. The nvm repo has moved to https://github.com/nvm-sh/nvm. Obviously this has not broken this package - just letting you know.

I was confused about it until I went back in the commits and verified that the same repo used to belong to Tim (creationx) and has been removed from its old location.

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

Downloaded source filenames must be unique, for those who set SRCDEST in /etc/makepkg.conf. See https://wiki.archlinux.org/index.php/PKGBUILD#source

Please add something like this to the beginning of source:

source=("${pkgname}-${pkgver}.zip::https...

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

Installation and running the init-nvm.sh 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 ?

@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 nvm.sh to be in $NVM_DIR.

@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.

[0] https://aur.archlinux.org/packages/nvm-git/

EDIT: I've pushed the change here too.

@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 nvm.sh inside $NVM_DIR. This is solved with ln -s /usr/share/nvm/nvm.sh $NVM_DIR/. Can you add that to the same script that copies nvm-exec?

@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.

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

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

@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.

@tomwadley same error :/

@hutliver I'm not sure what's happening here. Can you try removing this package and installing nvm the "official" upstream way with their install.sh curl|bash?

Hi! Facing this error with the package, there's no relevant info.. bash: /usr/share/nvm/nvm.sh: line 62: syntax error near unexpected token }' bash: /usr/share/nvm/nvm.sh: line 62:}' bash: /usr/share/nvm/bash_completion: line 48: syntax error near unexpected token }' bash: /usr/share/nvm/bash_completion: line 48:}'

using termite

@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/init-nvm.sh" which you can source in your .bashrc to get nvm working.

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.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm

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

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

EDIT: the wiki has been updated.

@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.

@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 https://aur.archlinux.org/cgit/aur.git/tree/nvm.install?h=nvm

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?

Note that for init-nvm.sh 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.

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!

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

@Depado This package doesn't create that file. I think that file is created by the official install.sh 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 install.sh script.

Just a heads up, when uninstalling the package, /etc/profile.d/nvm.sh 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)

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

Check out https://aur.archlinux.org/packages/nodejs-fake/ which takes care so packages like npm don't install nodejs as their dependency, keeping nvm the only source of nodejs on the system.