search

dominictarr / npmd

MIT License
450 stars 37 forks source link

WARN! expected …NaN… #14

Closed garthk closed 11 years ago

garthk commented 11 years ago

When I npmd install, I get warned…

WARN! expected verror@1.3.6NaNb867ce391ebd872200fefc5c36505bfbe1e8fc81
WARN! expected backoff@2.2.0NaN75e57bf77a12ec2e756b83a3e55758d1945ba83d
WARN! expected formidable@1.0.14NaN77531a1be1baefef3ad84373ac1ab3bc75d239a3

I suspect you intend something other than NaN wedged between the version and the hash.

dominictarr commented 11 years ago

fixed in npmd-install@3.0.6

If you reinstall npmd you should get the fix.

garthk commented 11 years ago

Thanks. No more NaN.

I was still getting these…

npmd install event-stream@~3.0.14
WARN! expected stream-combiner@0.0.0 to have shasum=227980ce853938e54e4c28463d3e5e496c845f4d
WARN! expected duplexer@0.0.2 to have shasum=a8e6369d5ae85f77f832c2e67348f4fd5e186f7f
WARN! expected duplexer@0.0.4 to have shasum=3d8e199c895711c70cdf7c16cfc99d09c2760540

… but deleting my .npm directory fixed the problem.

dominictarr commented 11 years ago

npmd checks that the hash is as expected when it unpacks a file. For complicated historical reasons, npm unpacks, and then repacks the tarballs, which gives them a different hash. So, when the file is unpacked it's wrong.

It is planned to fix this in npm eventually, but the files downloaded by npmd directly will have the correct hash.