Npm 安装找不到模块“semver”

Question

I can't use npm install using the command prompt in NodeJS. I'm getting these errors when running npm install :

module.js:339
    throw err;
    ^
Error: Cannot find module 'semver'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (C:\Users\admin\AppData\Roaming\npm\node_modules\npm\l
ib\config\defaults.js:6:14)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)

Answer 1

I had the same error. npm uninstall npm -g , rm -rf node_modules didn't help me, because when I tried I was getting Error: Cannot find module 'semver' . But I solve my problem with these steps (this will delete other global modules you may be using):

• sudo rm -rf /usr/local/lib/node_modules
• sudo rm -rf ~/.npm
• brew uninstall --force node
• brew install node

Hope this will help those who are getting a similar problem.

Answer 2

I'm facing the same issue here.

If this occurs right after you run brew install yarn try running yarn global add npm and voilà - fixed!

Answer 3

如果您在 Linux 服务器中，请从服务器退出并重新 ssh

Answer 4

在 MS Windows 上，解决方案是删除%APPDATA%\npm并重新安装node

Answer 5

I had this too, after running brew install yarn yesterday. At least, everything was fine up until then.

I ran rm -rf node_modules and tried to reinstall, but no npm command was working.

In the end I took the rather simple step of reinstalling Node via the official Node installer for Mac OS X.

https://nodejs.org/en/download/

Everything is fine now. Just went back to the directory, ran npm install and it's done the trick.

Answer 6

On Ubuntu, if you would rather manage Node through the default repositories using apt , it's best to install both nodejs and npm this way.

It's very likely that the version of npm you are using is expecting semver in a specific place that is not aligned with the version of Node JS you have installed. If there is only one version of nodejs and only one version of npm , and they are both installed using the default repositories, this should work perfectly.

Here is my best guidance for getting Node and npm working using the main Ubuntu repositories:

0. sudo apt-get purge nodejs --auto-remove and sudo apt-get purge npm --auto-remove
1. whereis node : remove all the versions of node, one at a time. Repeat until this command returns a blank after node: .
2. sudo apt-get install nodejs
3. node --version : should return ... no such file or directory
4. nodejs --version : should return v1x.xx . This is the version installed by apt . It will probably be less recent that the latest version available on the Node JS website.
5. sudo apt-get install npm
6. npm --version : it will use the nodejs installed by apt and work correctly.

Answer 7

On Arch Linux what did the trick for me was:

sudo pacman -Rs npm
sudo pacman -S npm

Answer 8

I had the same problem, the way i solved it was by executing

PATH="$PATH"

in terminal, problem was the terminal kept the old path of nodejs instead of using the new one.

Answer 9

刚刚在 Arch Linux 4.13.3 上遇到了这个问题，我通过简单地重新安装semver解决了这个问题：

pacman -S semver

Answer 10

Actually, it is taking the reference of previously stored modules.

Solution:Delete the npm-cache/npm folder in the installation directory of nodejs. In windows, it is in C:/User/Username/Appdata/Roaming/npm(or npm_cache). and try to install again.

Same thing to do in any OS.

Answer 11

In my case on macOS(10.13.6), when I executed the following command

npm install -g react-native-cli

I got this error

Error: Cannot find module 'semver'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:690:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/unsupported.js:2:14)
    at Module._compile (internal/modules/cjs/loader.js:776:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
    at Module.load (internal/modules/cjs/loader.js:653:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
    at Function.Module._load (internal/modules/cjs/loader.js:585:3)

The error got resolved after executing the command

yarn global add npm

proposed by @Ashoor

Answer 12

For me, this happened after I installed yarn globally. To resolve this issue, install npm using yarn and done.

yarn global add npm

Answer 13

sudo rm -rf /usr/local/bin/npm /usr/local/share/man/man1/node* ~/.npm
sudo rm -rf /usr/local/lib/node*
sudo rm -rf /usr/local/bin/node*
sudo rm -rf /usr/local/include/node*

sudo apt-get purge nodejs npm
sudo apt autoremove

Then install node and npm

Answer 14

在 Windows 上，再次下载Node 的 MSI并进行“修复”对我有用。

Answer 15

I had the same issue but it was caused by a broken package-lock.json file.

Deleting package-lock.json and running npm install again fixed it for me.

Answer 16

只需确保已安装semver ： npm install -g semver

Answer 17

Just uninstall node js then reinstall it using nvm. Your problem will be solved. I am a debian 10 user.

mahedi@debain:~$ curl -o-https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.2/install.sh | bash

after executing the command. close your terminal and reopen then run this command to install node js latest version.

mahedi@debain:~$ nvm install v14.15.5

now check by typing node -v

Answer 18

This worked for me on Ubuntu (latest version dated Oct/2020)

I had to first get code from the bash source:

curl -sL https://deb.nodesource.com/setup_14.x | sudo -E bash -

This got the latest version of node which updated my libraries and got rid of the 'semver' error.

Answer 19

For arch linux

sudo pacman -Rsc -n nodejs
sudo pacman -Sy nodejs
sudo pacman -Sy npm

Found here: https://github.com/npm/npm/issues/15558

Answer 20

I got same error and I solved it.

delete package-lock.json file and node_modules folder then npm install

Answer 21

First you can try close current terminal tab and open new its work fine

Answer 22

Faced this issue when I ran npm install using a lower version of node. Then later when I upgraded to latest version of node and ran gulp , it has shown this error.

To resolve, deleted node_modules and re-ran npm install . Then gulp ran fine.

Answer 23

Just a reminder of executable npm execute via node env:

xb@dnxb:/tmp$ type -a npm
npm is /usr/bin/npm
npm is /bin/npm
xb@dnxb:/tmp$ realpath /usr/bin/npm /bin/npm
/usr/share/npm/bin/npm-cli.js
/usr/share/npm/bin/npm-cli.js
xb@dnxb:/tmp$ 
xb@dnxb:/tmp$ head -1 /usr/share/npm/bin/npm-cli.js
#!/usr/bin/env node

I can check which node is chosen by type -a , the first line has the most priority, ie I can get same error if I run /usr/local/bin/node /usr/share/npm/bin/npm-cli.js , but no error if I run /usr/bin/node /usr/share/npm/bin/npm-cli.js :

xb@dnxb:/tmp$ type -a node
node is /usr/local/bin/node
node is /usr/bin/node
node is /bin/node
xb@dnxb:/tmp$ realpath /usr/local/bin/node
/usr/local/bin/node
xb@dnxb:/tmp$ realpath /usr/bin/node
/usr/bin/node
xb@dnxb:/tmp$ realpath /bin/node
/usr/bin/node
xb@dnxb:/tmp$ 

There are 2 unique node exe based on realpath . If you have the similar case, then you need to find out how to remove the undesired/broken node exe, eg sudo rm /usr/local/bin/node or manipulate env $PATH .

Answer 24

Just remove the /node_modules folder and try again. ;)

You can use npm rm to remove it.

You can also check this issue on GitHub. To be more specific about unnistal, try to follow this :

Uninstalling

So sad to see you go.

sudo npm uninstall npm -g Or, if that fails,

sudo make uninstall More Severe Uninstalling

Usually, the above instructions are sufficient. That will remove npm, but leave behind anything you've installed.

If you would like to remove all the packages that you have installed, then you can use the npm ls command to find them, and then npm rm to remove them.

To remove cruft left behind by npm 0.x, you can use the included clean-old.sh script file. You can run it conveniently like this:

npm explore npm -g -- sh scripts/clean-old.sh npm uses two configuration files, one for per-user configs, and another for global (every-user) configs. You can view them by doing:

npm config get userconfig # defaults to ~/.npmrc npm config get globalconfig # defaults to /usr/local/etc/npmrc Uninstalling npm does not remove configuration files by default. You must remove them yourself manually if you want them gone. Note that this means that future npm installs will not remember the settings that you have chosen.

Answer 25

I finally figured this out! Yes, you have to uninstall/delete all files and reinstall. BUT SOME OF THE FILE PATHS ARE TOO LONG TO DELETE DURING THE UNINSTALL PROCESS. The file paths are so long in Node that they may not be able to be deleted. You have to rename the file paths.

After uninstalling Node, use Command Prompt, navigate to ...\Appdata\roaming\ (use the path from the error message). Try to delete the folder with del npm. Then, if it doesn't allow you to delete a folder, start renaming the folders in the file path in the next error message to "a" or something short. You may have to do this for multiple folders along the path. Then you should be able to delete! Then reinstall node and it should work.

Answer 26

just remove your node_modules

rm -rf node_modules

than

yarn

or

npm install

Answer 27

Just delete (or rename) the cloned repository's version of semver folder: "gitClonedRepository/App/node_modules/semver"

and copy the "semver" folder from "C:\Program Files\nodejs\node_modules\npm\node_modules\semver"

into the application's node_modules folder.

(if you're on Windows, othervise it must be located somewhere in /usr/local/lib/node_modules).

Answer 28

我所需要的只是我正在工作的目录中的sudo rm -rf node_modules/ 。这发生在我用n lts更新我的节点版本之后

Answer 29

Nevermind install Yarn.Performs parallel installation resulting in better speed and performance from npm

 sudo apt remove yarn curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add - echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/sources.list.d/yarn.list sudo apt-get update sudo apt-get install yarn -y

Answer 30

就我而言，只需重新运行brew install yarn即可解决问题。

Answer 31

I faced with same trouble after brew installs yarn on my MacOs Sierra 10.12.6. (And the first try of installation fall after brew update self with a message " Homebrew must be run under Ruby 2.3! You're running 2.0.0. (RuntimeError)". So I re-run it.)

So I use n manager to reinstall npm.

• switch to another node version (for my case to 8.0) by "n" command with empty parameters
• or install new by "n xxx" where xxx the node version number (i need 6.9.1)
• delete working version by "n rm xxx" where xxx the node version number. use sudo if need
• install working version by "n xxx" where xxx the node version number. use sudo if need
• switch by to the working version of node. (see first step for reference)

I think the trouble can be caused that node was installed under sudo for case.

Answer 32

For Mac users, I tried installing a bunch of new node versions and uninstalling different ones. That didn't fix it. You have to completely wipe out all your installations first. Follow these instructions... How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X) .

Then download the latest version of node.

Answer 33

I had the same issue installing on AWS Linux. I had to install it with sudo . So to get around this I followed step 3 from this article (making sure to get the latest version of node)

https://www.hostingadvice.com/how-to/update-node-js-latest-version/

wget https://nodejs.org/dist/vx.x.x/node-vx.x.x-linux-x64.tar.xz
tar -C /home/aUser/node --strip-components 1 -xJf node-vx.x.x-linux.x64.tar.xz

But installed it to the user's home directory /home/aUser/node . Then added that path to my PATH.

export PATH=/home/aUser/node/bin:$PATH

After that I was able to do an npm install with no issues.

Answer 34

I faced this issues while running project on higher version of cli. To solve this issue you can simply comment out @angular-devkit/build-angular module and again you have to reinstall it through

npm install @angular-devkit/build-angular --save

Answer 35

For me, it happened while upgrading to gulp 4 from gulp 3 in my project. So, when I run "gulp watch" command, it was throwing me same error.

It's probably due to version mismatch as compared to my globally installed gulp.

So, either upgrading gulp with "-g" global flag would help, or else I followed this below

However, I used "./node_modules/.bin/gulp watch" in my project. This ensures that all the dependencies that gulp needs are taken from node_modules only.

Answer 36

i was getting an error saying Permission Denied after running any 'ng' command (ng --version). I googled for a while and tried clearing npm cache npm cache verify , uninstalling my global angular cli ( npm uninstall -g @angular/cli ) and reinstalling Angular/cli ( npm install -g @angular/cli ) etc.. but it would give an error say its already installed. but the node_modules folder here wouldn't have any angular folder.. reinstalled node even then restarted my computer.

ANSWER: Finally I found that the ng.cmd and ng.ps1 files in C:\Users\JaGoodwin\AppData\Roaming\npm\ here were still there (in npm folder).. even though I did npm uninstall -g @angular/cli . those files were causing ng (angular/cli) to think it was still installed. i deleted those files then npm install -g @angular/cli@8.3.29 (version i need) I then removed my projects node_modules and then ran npm install and now can run my angular project using ng serve .

C:\Users\JaGoodwin\AppData\Roaming\npm\

Find this by folder searching %APPDATA% in your windows search bar.

Answer 37

Start fresh.

brew uninstall --force node
brew install node

Answer 38

I can't use npm install using the command prompt in NodeJS. I'm getting these errors when running npm install :

module.js:339
    throw err;
    ^
Error: Cannot find module 'semver'
    at Function.Module._resolveFilename (module.js:337:15)
    at Function.Module._load (module.js:287:25)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (C:\Users\admin\AppData\Roaming\npm\node_modules\npm\l
ib\config\defaults.js:6:14)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)

Answer 39

On WSL (so, ~Ubuntu), I faced this problem after having installed both, nodejs and npm through apt , then updated Node using n .

I was able to resolve it by completely removing apt's installation of npm: sudo apt purge npm .

Answer 40

This issue usually comes when node js and npm versions are not compatible. To fix this in Ubuntu (my version was 20)

1. Uninstall node js and npm.
   • apt remove npm
   • apt remove nodejs
   • which node (it will return node js files path)
   • Delete node directory
2. Install NVM
   • Installation
3. Install node
   • nvm install eg nvm install 8.16
   • Above command will itself install node js and its compatible NPM.

Answer 41

Just check your preinstall scripts if you have one. Sometimes to restrict the versions of node and npm one needs to run a project.

If that's the case you need to install semver manually via npm install -g semver

Answer 42

我遇到了同样的问题并通过升级我的Node版本来修复它