Error cannot find module npm cli js

Ah, I had a similar problem with the linux-x64 version v10.15.3 on the Ubuntu subsystem for Windows 10, and suspect it is probably the same problem across multiple platform distributions.
The issue is the scripts for npm and npx aren’t even calling the correct files and are also using relative paths incorrectly!

I did the following to fix:

1. Locate nodejs bin
   Ubuntu Example:

which node
/usr/local/lib/nodejs/node-v10.15.3-linux-x64/bin/node

1. Navigate to NodeJS bin
   Ubuntu Example:

cd /usr/local/lib/nodejs/node-v10.15.3-linux-x64/bin

1. View the problematic scripts
   Ubuntu Example:

cat npm
../lib/node_modules/npm/bin/npm-cli.js

cat npx
../lib/node_modules/npm/bin/npx-cli.js

1. Shake/smack head
   Ubuntu Example:

1. Rename (or remove) the bad files
   Ubuntu Example:

mv npm npm-wrong

mv npx npx-wrong

1. Replace bad files with relative symbolic links to the correct locations
   Ubuntu Example:

ln -s ../lib/node_modules/npm/bin/npm npm

ln -s ../lib/node_modules/npm/bin/npx npx

1. Also add a symbolic link to the node_modules directory itself, because another broken reference occurs without it
   Ubuntu Example:

ln -s ../lib/node_modules/ node_modules

1. Test
   Ubuntu Example:

cd ../../..

pwd
/usr/local/lib

npm version
{ npm: '6.4.1',
  ares: '1.15.0',
  cldr: '33.1',
  http_parser: '2.8.0',
  icu: '62.1',
  modules: '64',
  napi: '3',
  nghttp2: '1.34.0',
  node: '10.15.3',
  openssl: '1.1.0j',
  tz: '2018e',
  unicode: '11.0',
  uv: '1.23.2',
  v8: '6.8.275.32-node.51',
  zlib: '1.2.11' }

1. Post about discovery on Github Issue Tracker
   Example:
   Error: Cannot find module ‘C:Program Filesnodejsnode_modulesnpmbinnode_modulesnpmbinnpm-cli.js’ #1618 (comment)

Can’t run npm on node 18.12.1 on Linux #45329

Version

18.12.1 (the archive downloaded directly from site)

Platform

Linux 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

When I edit node-v18.12.1-linux-x64/bin/npm from:

The problem will be solved. But I don’t how to make contribution, because I can’t understand your source code.

The text was updated successfully, but these errors were encountered:

Can we try rm -rf node_modules/ && npm I and please paste the results for better debugging.

Also, is it possible to make a test code snippet?

Got this too. Such issues do not occur on nvm or nodesource, only with archive downloaded directly from site.
Devs must be joking. I simply download archive, untar it in /opt/, set PATH to /opt/node/bin.

node —version is working

npm only works with change above

npx also needs a patch:

Sorry, I am dumb fox, looks like false alert

When I leave node binary archive in /home and rename it to node19 it works just fine. This is what I have in .bashrc:

having it in /opt with root owner and 755 produces issues above. How should I set permissions correctly?

Version

Platform

Linux 5.15.0-52-generic #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

What steps will reproduce the bug?

How often does it reproduce? Is there a required condition?

What is the expected behavior?

What do you see instead?

Additional information

When I edit node-v18.12.1-linux-x64/bin/npm from:

The problem will be solved. But I don’t how to make contribution, because I can’t understand your source code.

I also have this issue

Hello! I`m trying to deploy nodejs app on AWS ubuntu EC2 micro instance. I have Node 18.12.1. When I start from my local folder in the remote terminal — it works well. But when I run as a demon — node throws an error where I use an ‘import’ statament. When I reconfiged a package.json file — the app works well

I have the same problem on a PC on Windows . After update Node version. Can any fixed this problem?

I had the same issue running rm -rf node_modules && npm i fixed it for me.

Источник

Cannot find module ‘..node_modulesnpmbinnpm-cli.js’ when running «gradlew -Pprod bootRepackage» #1829

I am new to this, so please bare with me. What I am doing is trying to deploy my jhipster code. For that I need to build war file. So I run the command gradlew -Pprod bootRepackage in command prompt. My project has no node_modules folder and so it is throwing error : Cannot find module ‘..node_modulesnpmbinnpm-cli.js’ .

The text was updated successfully, but these errors were encountered:

This is an NPM installation problem, not a JHipster bug.

Have a look at the NPM documentation, you have nice videos etc: https://docs.npmjs.com/

But why is it looking for node_modules folder in my project instead of the global folder where npm is installed?

If your project has no node_modules folder, it’s because the install phase after generation did no succeed or you did not follow the procedure in our doc.
Run it manually:

Got It @gmarziou . Actually I created the Jhipster project on a different machine and committed the code to be run on my machine. Now node_modules folder path is in .gitignore, so not committed. Should I remove the node_modules from .gitignore and recommit or I have to run npm on my machine again?

If node_modules is not existing ./gradlew -Pprod bootRepackage executes npm install , so you should keep node_modules ignored. Which version of the generator are you using? Which operating system are you using?

All Right. I am using windows and the latest version of Jhipster: 2.19.0

I ran the following command on windows cmd: gradlew -Pprod bootRepackage. It Build Successfully but it did not generate any node_modules folder.

Okay, I can’t check it now on windows. @deepu105 Can you try it? But it sounds like a npm missconfiguration.

One more thing. If I run yo jhipster:cloudfoundry from windows it gives error: The goal you specified requires a project to execute but there is no POM in this Directory. Please verify you invoked maven from the correct directory.

Now since it is supposed to be a gradle build how can we make cf understand this.
I found something here (Can we use this?): https://github.com/cloudfoundry/cf-java-client/blob/master/cloudfoundry-gradle-plugin/README.md

I’ve been having the same issue trying to build on Windows. I was able to figure it out. Put the following in profile_prod.gradle :

Gradle will then download and install node and npm to the project’s node_modules folder before running npm install.

For some reason Gradle is trying to use node/npm in the project’s local npm_modules folder instead of what’s in the PATH. This may be a bug with the Gradle node plugin, but I haven’t done enough investigation to know where the problem lies for sure. See srs/gradle-node-plugin#64

Edit: JHipster 2.20.0 requires at least node 0.12.0 but the plugin will download 0.11.10 by default, so you will need to specify the version. I updated the config to reflect this.

Источник

Unable to find npm-cli in node-modules folder #636

NVM4W version: 1.1.7

My Environment

Windows 10 Enterprise version 20H2 19042.867

Expected Behavior

I want to be able to use NPM

Actual Behavior

npm —version
internal/modules/cjs/loader.js:613 throw err; ^ Error: Cannot find module ‘C:UsersvkotulskyiAppDataRoamingnvmv12.0.0node_modulesnpmbinnpm-cli.js’

The text was updated successfully, but these errors were encountered:

This is the same as issue #476 that was marked as «resolved».

As a workaround, I had to install NodeJS separately from https://nodejs.org/en/download/. Now npm is installed globally into «C:Program Filesnodejs»npm . After installation, I can now switch between different versions of NodeJS using nvm use , though it always uses the globally installed npm .

I’m using yarn as a package manager, so while this workaround is disappointing, I can probably live with it.

Uggh. My workaround did not persist. After another invocation of nvm install , when I next ran npm , it failed in the same way. So once again, I reinstalled 14.16.1 and it worked again.

Same problem here. First time I tried I was behind a corporate firewall (like someone mentioned in the other issue), but the attached screenshot was on a wide-open internet. Seems to me like the biggest issue isn’t that it fails to install npm, it’s that it acts like everything went fine. Some sort of error message would be great!

Setting environment vars HTTP_PROXY and HTTPS_PROXY , then uninstall and re-install worked for me. curl for Windows uses HTTP_PROXY , too.

@Marcuse7 Of what value should I set HTTP_PROXY and HTTPS_PROXY to?
Thank you in advnace.

@Marcuse7 Of what value should I set HTTP_PROXY and HTTPS_PROXY to?
Thank you in advnace.

I am come from China.I must use a proxy to connect github.The value is my local proxy url:port.
If you used powershell, maybe you can set the terminal proxy.

I’m not behind a proxy to access to Internet, and I have the same error. Any other solution?

I ended by uninstalling this package and using Volta

I did some digging into this and, if proxies are not your issue, this may be caused by using nvm to install a new version of node from a non-elevated prompt (either CMD or PowerShell). If this was the issue, you’ll need to uninstall the version of node causing the issue through nvm and reinstall it with nvm under an administrative/elevated prompt. It appears that @Weicocu was correct in that the npm installation is silently failing when it’s not elevated.

I think something is going wrong somewhere here: https://github.com/coreybutler/nvm-windows/blob/master/src/nvm.go#L284-L306. This code moves the dowlonaded NPM sources to C:Program Filesnodejsnode_modulesnpm , and for some reason C:Program Filesnodejsnode_modules ends up being empty.

I tried to reproduce what the source code does, and made it work, that confirms the above.

1. Install NVM
2. nvm install ; nvm use (where is the version you want)
3. Go to https://nodejs.org/dist/index.json and find node of . In the object containing , remember the value of the npm field. Now it’s
4. Go to https://github.com/npm/cli/archive/ .zip — this will download the missing NPM sources
5. Unzip the downloaded archive to
6. Copy to C:ProgramDatanvmv node_modules
7. Rename C:ProgramDatanvmv node_modules to C:ProgramDatanvmv node_modulesnpm
8. NPM now works

I ran into this issue after using nvm to install Node 10.16.3 and then Node 14.17.2 on Windows 10 Enterprise (21H1). I had uninstalled an existing version of Node 10 prior to installing nvm .

I was able to resolve it by using nvm to uninstall both versions, and then nvm install Node 14.17.2 first, then Node 10 — that seemed to fix it.

I also tried running cmd.exe as an Administrator, and then using nvm with those privileges, but that didn’t seem to resolve the situation (but maybe it cleared something without my knowledge).

Same problem here. First time I tried I was behind a corporate firewall (like someone mentioned in the other issue), but the attached screenshot was on a wide-open internet. Seems to me like the biggest issue isn’t that it fails to install npm, it’s that it acts like everything went fine. Some sort of error message would be great!

For anyone that would be have this problem. I can say that, in my case i discover that problem is happening when i’m running the installer from a different partition to windows was installed.

So when i reinstall using nvm-setup.exe from C: partition, all is installed an npm is finded without problems. no need to modify enviroment variables in my win10.

I know that this looks crazy, but i think that this can be usefull to developers resolve this issue, or anyone need help for this now.

Having this same issue today, 26 August 2021.
Node installs work fine, but npm does NOT install.
so nvm-windows is not usable.

This line in the current commit source references a URL location from which to download npm zip files during the install process:

var npmBaseAddress = «https://github.com/npm/cli/archive/»

but the URL referenced there is not accessible:
https://github.com/npm/cli/archive/

(EDIT: This appears to be an intermittent GitHub/network issue? Sometimes the archive file can be downloaded from here, with a 302 redirect, but sometimes it fails! It happens often enough to be a problem for quite a few people in several related issue/comments.)

That file location did not currently exist (404) (at the moment of writing).

This is the line that builds the npm URL plus zip file name:

So the current version of nvm go source code is reaching out to this unreachable URL:
https://github.com/npm/cli/archive/v6.14.15.zip

when it could/should be reaching out to this URL (which IS a valid download link):
https://github.com/npm/cli/archive/refs/tags/v6.14.15.zip
(this link seems to be more stable.)

Maybe the npm team (or GitHub?) changed the default location for release/archive zip files for download?

Just speculating here.
Not sure if this is an issue for NPM team to resolve (should they maintain old zip files in an archive)?
Probably better to simply update nvm-windows to reference the «correct» stable URLs for release zip files, with the «/archive/refs/tags/» URL fragment?

It’s also unfortunate the the error handling does not catch this common issue. Maybe during a cleanup/validation step, the code should actually check that the files for node and npm were actually copied to the correct locations and exist? It’s strange that the download method doesn’t throw an error when the file can not be reached via URL (intermittently, I see now).

Ugly work around here.

Using a modification from this comment above:
#636 (comment)

I was able to get nvm versions to work by downloading the «real» npm zip release artifacts from this URL:
https://github.com/npm/cli/archive/refs/tags/v6.14.15.zip
then unzipping contents of the that archive folder (named ex. «cli-6.14.15») and copying those contents to the nvm node version node_modules directory under a new «npm» folder.

On my machine that translated to (when installing into a node v12 installation):
C:UsersAndrew.MurdochAppDataRoamingnvmv12.22.5node_modulesnpm

you will have to rinse and repeat for each separate node installation node_modules folder.

If the changes in my earlier comment made it into a PR for merge. that might solve the problem. Or maybe not as this may be a truly intermittent GitHub download issue, which makes fixing/trapping errors trickier, but not impossible. And even if a stable fix was submitted, it would not be available until a new nvm-windows release was generated.

Not sure it is worth the time as there haven’t been any new releases in quite a long time as referenced here by the author/maintainer:
#565 (comment)

When npm cannot be found, it means one of the following:

1. The node installation is invalid/corrupt
2. npm was not fully downloaded or transferred into the node root.
3. The user lacks appropriate permissions to execute a script.

In most cases, the node installation doesn’t have npm because node wasn’t installed with the appropriate permissions.

In NVM4W 1.1.9, logic was added to retry use if it fails due to permissions. To run nvm use , an account must have permissions to create directory symlinks (not just junctions). In Windows 10, this requires administrative privileges. In Windows 11, the OS still requires these permissions, but enabling developer mode will grant them. NVM4W attempts to run use «as-is». If the command fails with «access denied», NVM4W will automatically and silently re-run the command, this time presenting a UAC prompt. If you don’t accept the UAC prompt or do not have permission to run it, an «access denied» message will be presented. This should help prevent «bad» node installations.

I recommend upgrading to v1.1.9. If you still encounter this issue, reinstall the version of Node you want to run. The new version should handle these errors.

I’m closing this issue as I believe this is resolved in the latest versions.

Источник

If you try and run npm i and get Error: Cannot find module '../lib/cli.js', then you can easily fix the problem by running the following.

How does the error look?

Error: Cannot find module '../lib/cli.js'
Require stack:
- /usr/local/lib/node_modules/npm/bin/npm-cli.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function.Module._load (node:internal/modules/cjs/loader:778:27)
    at Module.require (node:internal/modules/cjs/loader:999:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/npm/bin/npm-cli.js:2:1)
    at Module._compile (node:internal/modules/cjs/loader:1095:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1147:10)
    at Module.load (node:internal/modules/cjs/loader:975:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/usr/local/lib/node_modules/npm/bin/npm-cli.js' ]
}

How to solve the Module Not Found error

brew uninstall --ignore-dependencies node
sudo chown -R $(whoami) /usr/local/*
brew cleanup
brew install node

This will uninstall and cleanup your previous node installation, making sure to set the correct permissions, before reinstalling it.

When you are working in Node, you will sometimes encounter the error Cannot find module 'module-name' with the error code MODULE_NOT_FOUND.

The error looks like this:

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

Error: Cannot find module 'module'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:793:17)
    at Function.Module._load (internal/modules/cjs/loader.js:686:27)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1043:10)
    at internal/main/run_main_module.js:17:11 {
        code: 'MODULE_NOT_FOUND',
        requireStack: []
    }

In this post, we’ll learn how to resolve this error.

What is the problem?

The issue is that Node is unable to find the module that you are trying to import into your Node application.

The most common reason for this is that you simply haven’t installed the project’s dependencies yet.

The project’s dependencies are listed in the package.json file at the root of the project.

The Solution

To fix the Cannot find module error, simply install the missing modules using npm.

To so, you can use the following command:

	npm install

If you are using the yarn package manager, you can use the following command:

	yarn install

This will install the project’s dependencies into your project so that you can use them.

Sometimes, this might still not resolve it for you. In this case, you’ll want to just delete your node_modules folder and lock file (package-lock.json or yarn.lock) and try again.

This is how you can delete the node_modules folder and lock files:

	rm -rf node_modules

rm package-lock.json
rm yarn.lock

Local files

If your module is not coming from a remote source, you are seeing the error because the path to the local file is not correct.

Try to confirm that the path pointing to the local module is correct and your error should be resolved.

Conclusion

The Cannot find module error is a common error that usually happens when dependencies are not installed. Once you install your dependencies and ensure that the paths are correct, you can resolve the error and run your application successfully.

Hopefully, this resolved the issue for you.

Thanks for reading!

• Support Us

• Join

• Share

• Tweet

• Share