Npm err error enoent

Common errors

Broken npm installation

If your npm is broken:

  • On Mac or Linux, reinstall npm.
  • Windows: If you’re on Windows and you have a broken installation, the easiest thing to do is to reinstall node from the official installer (see this note about installing the latest stable version).
  • Some strange issues can be resolved by simply running npm cache clean and trying again.
  • If you are having trouble with npm install , use the -verbose option to see more details.

No compatible version found

\AppData\Roaming\npm’ on Windows 7 permalink» >

Error: ENOENT, stat ‘C:\Users\ \AppData\Roaming\npm’ on Windows 7

The error Error: ENOENT, stat ‘C:\Users\ \AppData\Roaming\npm’ on Windows 7 is a consequence of joyent/node#8141, and is an issue with the Node installer for Windows. The workaround is to ensure that C:\Users\ \AppData\Roaming\npm exists and is writable with your normal user account.

You are trying to install on a drive that either has no space, or has no permission to write.

  • Free some disk space or
  • Set the tmp folder somewhere with more space: npm config set tmp /path/to/big/drive/tmp or
  • Build Node yourself and install it somewhere writable with lots of space.

You need to install git. Or, you may need to add your git information to your npm profile. You can do this from the command line or the website. For more information, see «Managing your profile settings».

Running a Vagrant box on Windows fails due to path length issues

@drmyersii went through what sounds like a lot of painful trial and error to come up with a working solution involving Windows long paths and some custom Vagrant configuration:

In the code above, I am appending \\?\ to the current directory absolute path. This will actually force the Windows API to allow an increase in the MAX_PATH variable (normally capped at 260). Read more about max path. This is happening during the sharedfolder creation which is intentionally handled by VBoxManage and not Vagrant’s «synced_folder» method. The last bit is pretty self-explanatory; we create the new shared folder and then make sure it’s mounted each time the machine is accessed or touched since Vagrant likes to reload its mounts/shared folders on each load.

npm only uses git: and ssh+git: URLs for GitHub repos, breaking proxies

I fixed this issue for several of my colleagues by running the following two commands:

One thing we noticed is that the .gitconfig used is not always the one expected so if you are on a machine that modified the home path to a shared drive, you need to ensure that your .gitconfig is the same on both your shared drive and in c:\users\[your user]\

You are trying to talk SSL to an unencrypted endpoint. More often than not, this is due to a proxy configuration error (see also this helpful, if dated, guide). In this case, you do not want to disable strict-ssl – you may need to set up a CA / CA file for use with your proxy, but it’s much better to take the time to figure that out than disabling SSL protection.

This problem will happen if you’re running Node 0.6. Please upgrade to node 0.8 or above. See this post for details.

You could also try these workarounds: npm config set ca «» or npm config set strict-ssl false

  • upgrade your version of npm npm install npm -g —ca=»»
  • tell your current version of npm to use known registrars npm config set ca=»»

If this does not fix the problem, then you may have an SSL-intercepting proxy. (For example,

Not found / Server error

  • It’s most likely a temporary npm registry glitch. Check npm server status and try again later.
  • If the error persists, perhaps the published package is corrupt. Contact the package owner and have them publish a new version of the package.
  • Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later.
  • This can be caused by corporate proxies that give HTML responses to package.json requests. Check npm’s proxy configuration.
  • Check that it’s not a problem with a package you’re trying to install (e.g. invalid package.json ).
Читайте также:  Ajax response json error

Many ENOENT / ENOTEMPTY errors in output

npm is written to use resources efficiently on install, and part of this is that it tries to do as many things concurrently as is practical. Sometimes this results in race conditions and other synchronization issues. As of npm 2.0.0, a very large number of these issues were addressed. If you see ENOENT lstat , ENOENT chmod , ENOTEMPTY unlink , or something similar in your log output, try updating npm to the latest version. If the problem persists, look at npm/npm#6043 and see if somebody has already discussed your issue.

cb() never called! when using shrinkwrapped dependencies

Take a look at issue #5920. We’re working on fixing this one, but it’s a fairly subtle race condition and it’s taking us a little time. You might try moving your npm-shrinkwrap.json file out of the way until we have this fixed. This has been fixed in versions of npm newer than npm@2.1.5 , so update to npm@latest .

npm login errors

Sometimes npm login fails for no obvious reason. The first thing to do is to log in at and check that your e-mail address on matches the email address you are giving to npm login .

If that’s not the problem, or if you are seeing the message «may not mix password_sha and pbkdf2» , then

  1. Log in at
  2. Change password at – you can even «change» it to the same password
  3. Clear login-related fields from

/.npmrc – e.g., by running sed -ie ‘/’

and it generally seems to work.

npm hangs on Windows at addRemoteTarball

Check if you have two temp directories set in your .npmrc :

Look for lines defining the tmp config variable. If you find more than one, remove all but one of them.

See for more about this unusual problem.

npm not running the latest version on a Windows machine


How to solve npm ERR! enoent This is related to npm not being able to find a file

Posted on Jun 25, 2022

Learn how to solve npm error code ENOENT: no such file or directory Photo from Unsplash

When running npm commands from the terminal, you may get an error with code ENOENT .

Here’s an example of the error message log when running the npm start command:

As you can see, there’s an error with code ENOENT that prevents npm start command from running successfully.

The code ENOENT means that npm fails to open a file or directory that’s required for executing the command.

The npm start command is used to run the start script in the package.json file.

When the package.json file isn’t found, then npm throws the ENOENT error.

To fix the error, you need to make sure that the file or directory needed for running the command is available.

In the case above, adding a package.json file to the project will solve the error.

If that doesn’t work, then you probably don’t have a start script in your package.json file.

Also, make sure that you are running the command from the project directory, right where the package.json file is located.

npm commands don’t work when you run them from a parent or child directory.

npm install fails with code ENOENT

The ENOENT error may also appear when you run the npm install command.

Here’s an example of the error:

The error above happens because you have a dependency that doesn’t install correctly.

Here are the steps to resolve this issue:

  • Make sure you are using the latest npm version
  • Clean your npm cache
  • Delete node_modules folder and package-lock.json
  • Run npm install again

Run the following commands one by one from the terminal:

The npm install command should now run successfully.

And that’s how you solve the npm error code ENOENT: no such file or directory error.

Level up your programming skills

I’m sending out an occasional email with the latest programming tutorials. Drop your email in the box below and I’ll send new stuff straight into your inbox!


Nathan Sebhastian is a software engineer with a passion for writing tech tutorials.
Learn JavaScript and other web development technology concepts through easy-to-understand explanations written in plain English.


NPM «ENOENT: no such file or directory error» when installing Sails.js dependencies with Node 8.9.4 LTS

I recently upgraded my computer and with it, to the latest LTS version of Node and NPM:

I have a Sails.js 0.12.14 application for which I’m trying to install NPM dependencies with npm install but when I do that, I get the following errors:

I can’t seem to figure out what’s going on and can’t find suitable answers anywhere else online. I even ran npm cache clean —force , rm -rf node_modules and retried with similar errors. It seemed to work fine when I was on Node

6 but after upgrading to Node 8.9.4 and NPM 5.6.0, it just won’t install my dependencies. How can I resolve this?

14 Answers 14

Try deleting the package-lock.json file.

For me, it turned out these errors were hiding the real underlying problem, which was that my credentials for a third-party npm repository (azure devops) had expired. I had to re-run vsts-npm-auth -config .npmrc to update the token in my .npmrc file.

No permission, no internet issue, it’s just a general issue of npm . I solved the problem with yarn.

Or you can use no-optional flag.

It may be a problem with the cache, try to verify the cache.

In my case, I tried deleting package-lock.json , clearing and verifing the npm cache, removing node_modules , even stopping the antivirus (W10 machine) and was still getting this error.

I somehow fixed it by running npm update before npm install , which creates a new package-lock.json :

Deleting and regenerating ‘package-lock.json’ usually solves this issue however that’s inherently risky because you will likely be upgrading multiple packages at a time.

In my case it turned out that there was one specific package version that package-lock.json was referencing, that was 5 levels deep in the dependency. That version no longer existed at the npm registry so it caused the install to break. I had to find which package was pulling in this dependency and upgrade that one to resolve the issue.

Just delete package-lock.json file and then install package(s) you want. All will work.

Just delete package-lock.json file and then install packages you want with npm install . All will work.

rm -rf node_modules

If the issue still persists check if you have a global version of any of the packages installed. This can happen if you have a global version of a package that clashes with a local version of a package.

I was struggling with this for awhile, and it seems be be related to the following.

Let’s say you have 3 modules, A, B and C

Module A includes B and C directly Module B also includes module C, in it’s package.json dependencies.

If your package.json dependencies in module A look like the following:

You will get the above error you mentioned, ENOENT, blah, blah in .staging

If on the other hand you include the module with the nested include first like:

The error goes away. This seems like a bug in npm with nested dependencies, and the error messages and logs were not very descriptive. Check your dependency tree and see if you have the described case, if so, that is your issue.


NPM: ENOENT: no such file or directory, rename

I was using gulp on the project, then i decide to deleted all the dev dependencies to switch to webpack, but every time i try to install using npm is get this error:

any idea what can be happening.

30 Answers 30

just delete package-lock.json file and then install packages, that’s all you need and should be works

When I got this error I looked for all running instances of node in my task manager (i use process explorer on windows) and close/kill all running instances of node. For me its often webstorm or vs code. After closing these programs and ensuring there is no running node process npm install works again.

cache verify command resolved the issue for me

I remove node_modules and package_lock.json . Then, npm install and it works

Iam using
node v15.5.0

  1. close «expo start»
  2. remove «package-lock.json»
  3. Try to install packages now

example: npm i @react-navigation/native

This will fix the issue.

The simplest fix for me was:

The second line may give a hint on what’s happening:

It looks like npm doesn’t have enough permission on the folder you’re trying to use.

  • Delete the npm_modules again.
  • Open whatever editor/terminal you’re using to npm install with admin permission.

I found a solution for the problem, apparently is some kinda problem with the last version of npm, i was using npm version 5.6.0 and i downgraded to npm version 5.3.0 . This did work after all, after intall a couple packages i still get the same error.

ok change version of npm for the last version 5.8.0 now everything working just perfect, before was some kind of problem with atom that denied the permission the building process to install the dependencies of the package.

I just retried to run

and it succeeded

For me, package-lock.json was not created and script was failing before itself.

This fixed my issue:

If you ever get this error, the hotfix is to follow these steps:

delete node-modules folder run command npm cache clean —force run command npm install install the package again with npm install your-package-name

Actually the current package you are installing has some dependencies which is not being found my npm. So, before installing this package just perform the following command. (It will install all your listed dependencies mentioned in package.json file which are necesaary to run your application)

For not to delete package-lock.json or node_modules every time, just add file «.npmrc» with content «package-lock=false», or add this string if file «.npmrc» already exists.

You can try by removing the package-lock.json with the command rm package-lock.json then you go to the Node.JS website you ‘install it’ by going to LTS then after your node is updated run npm install in your terminal and that worked for me.

Just update the node to the latest version. It solved my problem.

I was running command in Ubuntu wsl and it wasn’t working so i tried running in cmd prompt and it worked

Kindly check any package.json is open anywhere, then close it first then retry.

For me I just deleted both package-lock.json & node_modules folder. Now everything works great 😃

Another thing I’ve seen a lot on projects that have been around and gone through multiple contributors:

  • Double check to see if anyone on your team has simultaneously done a npm install and yarn .

The tell-tale sign is you’ll see a package-lock.json (generated by npm) and yarn-lock.json (generated by yarn) in the same repo. This can cause side-effects from collisions in the node_modules folder.

You can try dumping that folder locally, establishing a package manager of choice for your project and instructing the whole team on best practices.


Оцените статью