Fixing "npm ERR! code ENOTEMPTY" on npm set up

Introduction

On this Byte we’ll strive that will help you perceive and repair a standard npm error – “npm ERR! code ENOTEMPTY”. In the event you’ve been working with Node.js and npm, likelihood is you have encountered this error in some unspecified time in the future. However don’t be concerned, we’ll do our greatest to demystify it for you.

What’s “npm ERR! code ENOTEMPTY”?

“npm ERR! code ENOTEMPTY” is an error message that npm, the Node.js bundle supervisor, throws when it encounters a non-empty listing whereas trying to put in a bundle. The “ENOTEMPTY” a part of the error message is definitely a typical POSIX error code, which stands for “Error, Not Empty”. In less complicated phrases, npm is attempting to inform us that it could actually’t carry out the operation as a result of the goal listing isn’t empty.

Observe: The POSIX customary defines a set of working system interfaces to make sure compatibility between totally different methods. ‘ENOTEMPTY’ is without doubt one of the many error codes outlined on this customary.

Widespread Causes of the Error

The “npm ERR! code ENOTEMPTY” error sometimes happens when npm tries to switch a listing with a file in the course of the set up course of, however finds that the listing isn’t empty. This could possibly be attributable to a number of causes:

1. Concurrent installations: In the event you’re operating a number of npm installations concurrently, they could intervene with one another.
2. Earlier set up leftovers: If a earlier npm set up was interrupted or did not full efficiently, it might have left some information behind within the listing.
3. Guide modifications: In the event you’ve manually added information to the node_modules listing, npm would possibly throw this error when it tries to replace or exchange a bundle.

The unlucky reality about errors like these is that you just won’t

The best way to Repair “npm ERR! code ENOTEMPTY”

Now that we all know what causes the error, let us take a look at the right way to clear up it.

• Delete node_modules: There could also be a difficulty along with your node_modules listing that’s stopping npm from putting in a brand new module there. This could possibly be a corrupt state attributable to a earlier failed set up, manually altering contents of the listing, or one thing else. That is sometimes the answer that works for most individuals. Delete the listing with:

  $ rm -r node_modules
  

  To be protected, you may even delete the package-lock.json file to make sure you get a full re-install.

• Clear the npm cache: The npm cache is sort of a storage for downloaded packages. Typically, this cache can turn into corrupted, resulting in errors. You’ll be able to clear the cache utilizing the next command:

  $ npm cache clear --force
  

• Delete particular bundle: In the event you’re npm set up takes a really very long time and also you’d reasonably handle the precise downside, you’ll be able to strive simply deleting the problematic bundle. For instance:

  $ rm -r node_modules/my_module
  

  This fashion you’ll be able to take away solely the issue after which solely reinstall that bundle, rushing up the method.

Related Errors

Now, you could be questioning, what if I encounter an analogous error however not precisely the npm ERR! code ENOTEMPTY? Nicely, npm has a variety of errors that it could actually throw, and whereas all of them have totally different causes, lots of them could be mounted utilizing related options.

For example, npm ERR! code EEXIST is one other frequent error that happens when a file that npm wants to write down already exists. Much like the earlier options, this will typically be mounted by deleting the offending file and operating npm set up once more.

$ rm -rf offending-file
$ npm set up

One other error, npm ERR! code EACCES, happens when npm does not have the required permissions to write down to a file or listing. You’ll be able to typically repair this by altering the permissions of the file or listing with the chmod command.

$ chmod 755 offending-directory
$ npm set up

Conclusion

On this Byte, we have lined a couple of frequent npm errors, particularly the npm ERR! code ENOTEMPTY error. We have realized about its frequent causes and the right way to clear up it, in addition to different related errors and their options, broadening our understanding of npm and its quirks.