Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'

[ghost]

It's uncertain why I am getting this error after running npm cli command. Is it because nvm is pointing to that same path?

internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:747:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
internal/modules/cjs/loader.js:905
  throw err;
  ^

Error: Cannot find module 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
    at Function.Module._load (internal/modules/cjs/loader.js:747:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
    at internal/main/run_main_module.js:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

[ammarsecurity]

run this in the command line.

SET PATH=C:\Program Files\Nodejs;%PATH%

[hilfa007]

Thank you so much..It worked for me

[myabdi4]

What the ... how did that work?

[beingsimple89]

run this in the command line.

SET PATH=C:\Program Files\Nodejs;%PATH%

Thanks this helped me

[coreybutler]

Related detail: PATH order

[luisaraujoc]

thnks

[coreybutler]

For those arriving via Google, search the issues for this problem and review the wiki for answers. There are many reasons why this can happen. The issues have unique responses for different circumstances.

Also see: Common Issues

[vipul-nema]

I have tried all steps. I checked the nodejs folder in nvm root and C:\Program Files\nodejs. both have empty node_modules folder.
If any one can help . Please do.

[mgrayum]

+1 same problem here too

[coreybutler]

First, I recommend not using C:\Program Files because it is a protected directory which requires different permissions (elevated admin). Some folks, especially independent developers, won't have this problem. It's more common in corporate environments where user accounts are a little more restricted. I tend to use C:\nodejs for my NVM_SYMLINK.

It's also important to note that C:\Program Files\Nodejs is often used by other Node installers as the default. If you have Node installed before installing NVM4W, it will attempt to migrate the existing version for you, but it will fail if the Node process is in use/locked by another user. This is why most version managers suggest uninstalling prior versions of Node before installing the version manager (it's just safer).

The bottom line is 99% of the time this issue manifests as a result of insufficient permissions and/or conflicts with prior versions. I cannot recreate this in a clean Windows environment.

Update

Due to the fact so many people install NVM4W without knowing whether another installation exists or not (then wondering why it doesn't work), I've create a simple tool to test: pathfinder.exe.

[Xyz39808]

I have attempted to install a module (twspace-crawler in my case) and doing so appears to delete my copy of npm-cli.js including everything else residing in the same folder. Going to Settings>Apps&Features>Node.js>Repair will consistently restore those files for me.

[chandanprogrammer]

Yes! This suggestion really worked.

[Tuscan-blue]

Thanks a lot!

[bruno8moura]

+1 same problem.

I found that after "nvm install ..." the npm is downloaded as .zip under %NVM_ROOT%/temp but instead of, after download npm package, to copy the npm package to %NODE_ROOT%/node_modules the file .zip is excluded.

In order to work, we need to copy the downloaded package to node_modules manually, however we need to do it before the downloaded npm package is deleted.

[coreybutler]

NVM also extracts the zip file, copying relevant files to the NVM_ROOT. The zip file isn't necessary once this is complete.

The most common problem people experience is selecting a target directory their user account doesn't have permission to write to. In other words, NVM4W can download/extract npm, but doesn't have permission to copy the files to the target directory.

[diputest]

@coreybutler, does that happen same for mac devices too? If yes, how to give permission to write?

[coreybutler]

@diputest I don't know how nvm-sh does it on mac.

[Araza1994]

I am getting same issue. Please any one help me

[Araza1994]

Worked for me when uninstall node and delete all folders and files related to node and npm in C:\Users[USER_NAME}\AppData\Roaming folder (npm, npm-cache and capacitor etc) and reinstall node

[coreybutler]

Many of those experiencing this issue likely have a space in your username. Make sure you upgrade to NVM 1.1.8, which resolves the space and special character issues.

See the Common Issues for more help.

[futuredeveloper985]

sorry but this answer does not resolve this problem I have another issue like this
I can't install npx create-react-app on my computer. it shows cannot find the module.

npx create-react-app myapp
'-------\AppData\Roaming\npm' is not recognized as an internal or external command,
operable program or batch file.
node:internal/modules/cjs/loader:936
throw err;
^

Error: Cannot find module 'C:\Users----- \node_modules\create-react-app\index.js'
at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
at node:internal/main/run_main_module:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []

[coreybutler]

@futuredeveloper985 have you run nvm install x.x.x and nvm use x.x.x where x.x.x is the version of Node you want to use? The error message indicates npm cannot be found. In most cases, this is because nvm use hasn't been executed.

Another possible reason is npx may not exist. npx is not available in older versions of npm.

[Divyansh-singh08]

i have the same issue how to solve this type of issue can you plz guide me

[streamlifehd]

Help pls

Please create a tokens.txt file and place your token in it!

Process finished with exit code 1

[canotf]

可以删除window的环境变量后重启电脑，并重新建立NODE_HOME

[ShandanaShahid]

check your all files in folder, may be extra file named SERVER has been created.. Delete it... I faced the same issue... May be this will help..

[dev8871]

I was facing the same issue, and the best way to solve this issue is to delete nodejs and reinstall it. Make sure to change the path from program files to somewhere else.

[SomeDevWeb]

Yes, that removed the error for me too. Thanks!

[JihyoPark-github]

저도 지우고 다시 설치하고 폴더 확인하니까 folder안에 cli.js 파일이 있더니 실행이 되네요 ㅠ 감사합니당

[pranav-kallikkal]

It worked. Thanks!

[paololopez]

I solved this problem by removing the old path from node and npm and adding them again.

[safil-badarudeen]

i have been trying to solve this problem for whole day.this helped me to solve this problem .thanks brother

[yosiasz]

For Windows machines

1. uninstall all versions of nodejs from your pc using control panel and then cleanup/delete any version you might have out there manually
2. uninstall nvm using control panel
3. Delete nvm folder from your Roaming folder
4. Install nvm and for your nvm folder use C:\nvm and for your nodejs folder choose c:\nodejs
5. in c:\nvm folder there is a settings.txt file, it should contain the following
   root: C:\nvm
   path: C:\nodejs
6. I also had another node manager called volta which I had to uninstall

This worked on my laptop.

[noirlyrik]

worked for me, thanks!

[kgkoutis]

worked for me also

[phelps-oc]

I tried the above uninstalling and reinstalling in C:\nvm and node in C:node. I got the same error with the updated directory (Error: Cannot find module 'C:\mnt\c\node\node_modules\npm\bin\npm-cli.js'). I am using node v14.0.0 for an old project. Also in VS code I am using wsl2 and Ubuntu 22. I switched my terminal to use Git Bash and it installed npm fine them. Weird. Maybe this helps someone with a similar setup.

[coreybutler]

Please note that as of v1.1.11, there is now a nvm debug command that may help your troubleshoot these kinds of issues.

[ImranRH321]

[zhanguoru]

i do not know what happened. can not run NMP and dispay:Error: Cannot find module 'C:\TEMP\NodeJS\node_modules\npm\bin\npm-cli.js'
I found ..\npm can not find. i copy NPM folder to ..\node_modules from package.
it is running...

[dlgombert]

I don't know if this is helpful to anyone, but I tried all of these steps and other things as well and no resolution. Then I tried to install the same version that was installed on my WSL instance (19.6.1), and for whatever reason it installed perfectly with no issues and now works properly. There may be something that I did that fixed the underlying issue that I'm not aware of, or maybe this issue only pops up with certain versions of node, or ... 🤷

[lx78WyY0J5]

Multiple years later, this issue is still opend.

I followed many steps to debug this... that installing on somewhere without specials char or space 😭

The only fix for me ... dont trust spaces and install somewhere else this crap

[coreybutler]

I'm sorry you feel the software is crap. You're welcome to use something else or pay for custom support.

[lx78WyY0J5]

I'm sorry you feel the software is crap. You're welcome to use something else or pay for custom support.

I just found risible that a bug "solved" in v18+ isn't really, and that the default path by installer is not supported 🤣😂
Multiple years, and the only solution is do not add spaces or special char to the path 👎

And BTW fixed myself my src & root path

[coreybutler]

The space issue has been resolved for quite some time. Most people falsely assume path issues are about spaces when it is actually non-standard encoding used by Windows to write files in non-English locales. Seeing as that's the only version of Windows I have, testing fixes isn't exactly straightforward.

If you want to contribute something that would be accepted, a PR that supports reading/writing the settings.txt in ASCII or UTF-8 encoding would be a useful fix, assuming it resolves the special character issue for non-US editions of Windows.