Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Please run `npm cache clean`

Tags:

node.js

npm

ipfs

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.

like image 545
FLASH Avatar asked Jul 31 '18 07:07

FLASH


People also ask

How do I force npm to clear cache?

Run: “npm cache clean –force” are both not working and you still can't clear the cache, you can force clear the cache by running: npm cache clean --force or npm cache clean -f . This will force delete the npm cache on your computer.

Should I clean npm cache?

clean: Delete all data out of the cache folder. Note that this is typically unnecessary, as npm's cache is self-healing and resistant to data corruption issues. verify: Verify the contents of the cache folder, garbage collecting any unneeded data, and verifying the integrity of the cache index and all cached data.

Is there an npm clean command?

The npm clean-install command (or npm ci for short) is an in-place replacement for npm install with two major differences: It does a clean install: if the node_modules folder exists, npm deletes it and installs a fresh one. It checks for consistency: if package-lock.


2 Answers

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.

like image 127
infin80 Avatar answered Sep 29 '22 19:09

infin80


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...

like image 27
Salketer Avatar answered Sep 29 '22 18:09

Salketer