Github user r-kamath commented on the issue:
    @VipinRathor can you try removing `npm cache clear` from .travis.yml ? 
otherwise add `--force`.
    npm doc says.
    > All data that passes through the cache is fully verified for integrity on 
both insertion and extraction. Cache corruption will either trigger an error, 
or signal to pacote that the data must be refetched, which it will do 
automatically. For this reason, it should never be necessary to clear the cache 
for any reason other than reclaiming disk space, thus why clean now requires 
--force to run.


Reply via email to