CODEWITHSUNDEEP
node.jsnpmipfs
FLASH
FLASH

Reputation: 1271

Please run `npm cache clean`

I'm trying to install IPFS from herenpm install ipfs --save and it is giving me the error as

npm ERR! tar.unpack error reading /media/FLASH/Tech/IPFS/ipfs

npm ERR! addLocal Could not install /media/FLASH/Tech/IPFS/ipfs

npm ERR! Linux 4.15.0-29-generic

npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "ipfs" "--save"

npm ERR! node v6.9.2

npm ERR! npm v3.10.9

npm ERR! 0-byte tarball

npm ERR! Please run npm cache clean

I tried doing npm cache clean but still it is giving me the same error while doing npm install ipfs --save

I don't know why I'm getting this error. and how to avoid this error.

Upvotes: 91

Views: 645480

Answers (4)

Simon_Weaver
Simon_Weaver

Reputation: 145880

A 'non corrupted global cache' is not the same as a 'non broken node_modules' for a particular project.

Just got this when trying to run a simple Angular CLI command (Windows):

An unhandled exception occurred: Cannot find module './formats/index'

I verified the global cache was ok with:

npm cache verify

Then I deleted the contents of nodule_modules and ran npm install and everything worked again.

Not sure if there's an equivalent to cache verify for a project's node_modules, but I've had to purge it many many times. But it's good to verify the cache is sound first.

Upvotes: 0

user2830254
user2830254

Reputation: 71

npm cache clean doesn't work now

Type below command :-

1- npm cache verify

Read the error in terminal it will show you exact commands to run for solution. you might need to append --force

2- sudo chown -R 501:20 "/$path$/.npm". (this works for me )

Upvotes: 7

infin80
infin80

Reputation: 1863

As of npm@5, the npm cache self-heals from corruption issues and data extracted from the cache is guaranteed to be valid. If you want to make sure everything is consistent, use npm cache verify instead. On the other hand, if you're debugging an issue with the installer, you can use npm install --cache /tmp/empty-cache to use a temporary cache instead of nuking the actual one.

If you're sure you want to delete the entire cache, rerun:

npm cache clean --force

A complete log of this run can be found in /Users/USERNAME/.npm/_logs/2019-01-08T21_29_30_811Z-debug.log.

Upvotes: 172

Salketer
Salketer

Reputation: 15711

This error can be due to many many things.

The key here seems the hint about error reading. I see you are working on a flash drive or something similar? Try to run the install on a local folder owned by your current user.

You could also try with sudo, that might solve a permission problem if that's the case.

Another reason why it cannot read could be because it has not downloaded correctly, or saved correctly. A little problem in your network could have caused that, and the cache clean would remove the files and force a refetch but that does not solve your problem. That means it would be more on the save part, maybe it didn't save because of permissions, maybe it didn't not save correctly because it was lacking disk space...

Upvotes: 8

Related Questions