My solution is to create symbolic links from the versions of node and npm I'm using to /usr/local/bin:

sudo ln -s "$NVM_DIR/versions/node/$(nvm version)/bin/node" "/usr/local/bin/node"
sudo ln -s "$NVM_DIR/versions/node/$(nvm version)/bin/npm" "/usr/local/bin/npm"
sudo ln -s "$NVM_DIR/versions/node/$(nvm version)/bin/npx" "/usr/local/bin/npx"

This makes npm, npx and node available to all users.

The below list of commands (source: digitalocean) seems to fix the problem

WARNING!!!! In some circumstances, these commands can break your system! Make sure you know what do these command do!!! related

n=$(which node); \
n=${n%/bin/node}; \
chmod -R 755 $n/bin/*; \
sudo cp -r $n/{bin,lib,share} /usr/local

The above command is a bit complicated, but all it's doing is copying whatever version of node you have active via nvm into the /usr/local/ directory (where user installed global files should live on a linux VPS) and setting the permissions so that all users can access them.

The fundamental reason is because nvm is not a real program. It's a bash function that gets loaded in the user's .profile, .bashrc, or ... So sudo doesn't automatically pick it up from the $PATH like most other programs.

An alternative node version manager is n: https://github.com/tj/n . That is a real program, so sudo will pick it up via the $PATH without any hacks (as long as sudo has /usr/local/bin in its $PATH).

sudo npm install -g n  # install 'n' globally
which n                # should be /usr/local/bin/n

sudo n lts             # need sudo to switch node versions
node --version         # v6.10.0
sudo node --version    # v6.10.0

According to README

When using nvm you do not need sudo to globally install a module with npm -g, so instead of doing sudo npm install -g grunt, do instead npm install -g grunt

Need sudo npm?

In my case, I need to sudo npm run start which needs the access to some file requiring root access. According to this issue,

You don't use sudo. You should instead chmod/chown the file so that the user that has nvm has access to the file;.

In sum

The maintainer of nvm strongly believe we don't need to sudo :P

Your problem is, that nvm is not in the path when you use sudo.

So type

$ which nvm

and the result will be something like

/home/abc/mynvm/nvm

Try again now with sudo:

sudo /home/abc/mynvm/nvm use v0.10.23

I assume you then run into the issue that the root user can't find the 0.10.13-version, but lets see the next error message...

I had your problem too. Finally I have worked around it. Here is my solution:

1. Uninstall nvm and nodejs. Here are some helpful links: Uninstallation of nvm. If you installed nodejs using apt-get, you can uninstall it with the command apt-get purge nodejs.
2. Install a global nvm. See this page : nvm global. As it says, "Standard nvm has known difficulties working in multi-user or rooted environments."

After restarting your terminal, you can run the command sudo nvm ls.

$ sudo bash -ic "nvm use stable; npm -v"
Now using node v6.3.1 (npm v3.10.3)
3.10.3

By extending @SimpleJ solution I have created a useful bash script that could be used to link all binaries from actual nvm bin dir to /usr/local/bin:

#!/bin/bash
. ~/.nvm/nvm.sh

DIR=$NVM_DIR/versions/node/$(nvm version)/bin/*
DEST=/usr/local/bin

for filename in $DIR; do
    filename=$(basename $filename)
    DEST_FILE=$DEST/$filename
    echo "Copying $filename to $DEST_FILE"
    sudo ln -sf "$NVM_DIR/versions/node/$(nvm version)/bin/$filename" "$DEST_FILE"
done

I have tried the same on my machine where I have nvm as well and I have a slighlty different response:

$ sudo node --version                                                                                                                                                                    
sudo: node: command not found

My guess is that you have installed node 0.11 outside of nvm. (Via package manager or even from source)

Therefore, running node via sudo would pick up this standalone node instead.

Does that make sense or am I mistaken?

I had installed nvm and node as an unprivileged user.

To use these as sudo, I added this to the superuser's .bashrc file:

$ sudo bash -c 'echo $HOME/.bashrc'
/root/.bashrc

Contents to add to /root/.bashrc (replace <your-user>):

# Lazy load NVM/NPM/Node
lazynvm() {
  unset -f nvm node npm
  export NVM_DIR=/home/<your-user>/.nvm
  [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"  # This loads nvm
}

nvm() {
  lazynvm
  nvm $@
}

node() {
  lazynvm
  node $@
}

npm() {
  lazynvm
  npm $@
}

The easiest solution to this will likely be to just hit the nvm.sh executable wherever it is.

sudo /home/ubuntu/.nvm/nvm.sh install node

This works fine for me (assuming that's the install path).

The full install procedure would look like

curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.0/install.sh | bash
export NVM_DIR="/home/ubuntu/.nvm"

[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

And then you can run the command above to hit the newly installed nvm.sh

I wanted to just install latest node-js from NVM API, without going for additional packages-purged versions. So I was looking to SUDO nvm install-latest-npm. Mb this will work for you - it definetely worked for me without installing/removing any apts. (Obviously change YOUR_USER_DIRECTORY for something suitable on ur system)

sudo /home/YOUR_USER_DIRECTORY/.nvm/nvm.sh | nvm install-latest-npm 

The simplest approach would be by making PATH variable to include your /bin location of your NVM_DIR. Here is the example:

export NVM_DIR="$HOME/.nvm"
  [ -s "/opt/homebrew/opt/nvm/nvm.sh" ] && \. "/opt/homebrew/opt/nvm/nvm.sh"  # This loads nvm
  [ -s "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm" ] && \. "/opt/homebrew/opt/nvm/etc/bash_completion.d/nvm"  # This loads nvm bash_completion

Add this line to make PATH variable contains your binary of Node from NVM

export PATH="$NVM_DIR/versions/node/$(nvm version)/bin:$PATH"

Hope it helps.