CODEWITHSUNDEEP
node.jsnpm
ChaseHardin
ChaseHardin

Reputation: 2269

Cannot run NPM Commands

I've been using NPM on my machine (Windows 10), but recently ran into an issue. I currently have Node.js installed and get the following error while running any npm command.

Question: What is causing this error and whats the best way to resolve it.

Command:

$ npm install

Output/Error:

bash: /c/Program Files/nodejs/npm: /bin/sh^M: bad interpreter: No such file or directory

Upvotes: 42

Views: 45870

Answers (13)

Marfullsen
Marfullsen

Reputation: 21

I had the same problem when I started using WSL, I solved it by using npm.cmd instead of npm command.

Upvotes: 0

Chris Halcrow
Chris Halcrow

Reputation: 32020

I got this error when running npm install in a Visual Studio Code terminal, using Powershell. I switched to use a WSL2 terminal inside Visual Studio Code instead and it worked (tip - use npm i as a shorthand)

Upvotes: 1

Laercio Metzner
Laercio Metzner

Reputation: 1359

It happened to me just now and all I had to do was exiting my wsl2 session and login in again.

Upvotes: 3

Chaka15
Chaka15

Reputation: 1371

If you already installed everything you need following this link https://learn.microsoft.com/en-us/windows/dev-environment/javascript/nodejs-on-wsl just try restarting your VS Code and trying to run npm install.

Upvotes: 1

Andreas Riedmüller
Andreas Riedmüller

Reputation: 1489

I encountered the same problem and found the cause and a simple solution.

After installing nvm in bash a few months ago, I recently decided to give zsh and on-my-zsh a try. I followed the instructions and installed zsh and oh-my-zsh. When trying to run node or npm I got the errror:

zsh: /mnt/c/Program Files/nodejs/npm: bad interpreter: /bin/sh^M: no such file or directory

My investigations led me to the $PATH variable. I then compared the output of echo $PATH in bash and zsh. In bash the path included the nvm directory, in zsh this directory was not added to the path.

The reason for this difference is that nvm adds a snippet to the end of .bashrc. In zsh .zshrc is loaded instead and the snippet will not be executed.

The snippet looks like this:

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

You can just copy these lines from .bashrc to the end of .zshrc, restart the shell, and the issue should be fixed if you have the same problem.

Upvotes: 1

Daniel Viglione
Daniel Viglione

Reputation: 9507

This command with 78 upvotes:

# export PATH=$(echo "$PATH" | sed -e 's/:\/mnt[^:]*//g') # strip out problematic Windows %PATH%

causes problems with other commands such as the "code" command for VS Code. It manipulates the $PATH. The correct solution here is to use nvm:

sudo apt-get install curl
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash
nvm ls
nvm use 14

Upvotes: 3

ZaneK
ZaneK

Reputation: 351

I had the same issue, I solved it by installing my dependencies on my Linux sub system as well. In my case it was just nodejs and npm.

  1. Open Ubuntu terminal(Windows Sub system) I'm on windows 10...

    sudo apt update

  2. Now that the system is up to speed, let's do...

    sudo apt install nodejs npm

(Do a variation of this suitable to you, I assume most are using nodejs though.)

My npm works now but still gives the error first. I mean it's not aesthetic at first, but my terminal on VS Code doesn't have the error first. Which is awesome!

TLDR: The linux subsystem doesn't have npm so download it there first.

Edit: formatting

Upvotes: 3

Aditya Malviya
Aditya Malviya

Reputation: 2149

I did with these commands.

sudo apt update && sudo apt install curl -y

curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash 

source ~/.profile 

nvm ls-remote 

nvm install v15 

node --version

Upvotes: 9

Adam 'Crashdoom' Walker
Adam 'Crashdoom' Walker

Reputation: 1318

Not my solution, but this seemed to work for me. Appears that having the Windows folder structure in $PATH while using WSL2 was causing that parse error, but I'm not exactly sure why.

  1. Go to your user root (cd ~)
  2. Open .bashrc in your chosen editor (vi, nano, etc.)
  3. Append to the end of the file: export PATH=$(echo "$PATH" | sed -e 's/:\/mnt[^:]*//g') # strip out problematic Windows %PATH%
  4. Close and re-open all terminal windows

Source: https://hackmd.io/@badging/wsl2#Troubleshooting-PATH

Updated: Per Lh Lee's comment, I've updated the regex from s/:\/mnt.*//g to s/:\/mnt[^:]*//g as this avoids accidentally capturing anything extra after the problematic /mnt paths.

Whereas the first regex will match /mnt/c/blah:/other/thing, the new one will not.

Upvotes: 116

Mohamed Dief
Mohamed Dief

Reputation: 21

Just faced the same issue, this issue happens because npm is installed on your windows machine but not on your WSL one. you just need to install npm on your linux machine then it will read the binary from linux not windows that's in case you want to use windows paths on your WSL. otherwise if you don't need the windows paths you can use thing adam mentioned by adding this into your path: PATH=$(echo "$PATH" | sed -e 's/:\/mnt.*//g') then refresh the shell with source ~/.bashrc

Upvotes: 1

Julius Limson
Julius Limson

Reputation: 526

experienced this problem on my wsl2

not a fix but a workaround. unmounting the c drive resolve the issue.

umount /mnt/c

Upvotes: 0

Aakash
Aakash

Reputation: 121

Install nodejs/npm using nvm and it will not conflict with the one in windows. The path for npm becomes (after installing using nvm) /home/ubuntu/.nvm/versions/node/v14.16.0/bin/npm

Read More about setting up your Node.js development environment with WSL 2

Upvotes: 12

mak
mak

Reputation: 1

I am using Git Bash for cli

I my case my Antivirus has quarantined the C:\Program Files\Git\user\bin\sh.exe file, and that is why $ npm init was not working and showing this error:

bash: /c/Program Files/nodejs/npm: /bin/sh^M: bad interpreter: No such file or directory

When I restored that file it started working normally.

Upvotes: 0

Related Questions