Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

ERR! shasum check failed for C:\Users\Indhu\AppData\Local\Temp\npm-13280-edd 76058\registry.npmjs.org\geoip-lite\-\geoip-lite-1.2.1.tgz npm ERR! Expected: 39c48ef93e498a259ece46bc9e98cf3ddb680d8b npm ERR! Actual: 2eeeef6f122b3567449d73d518c3490b95eb54b1 npm ERR! From: https://registry.npmjs.org/geoip-lite/-/geoip-lite-1.2.1.tg #19804

Open
2 of 13 tasks
Rejoyline opened this issue Feb 12, 2018 · 7 comments

Comments

@Rejoyline
Copy link

Rejoyline commented Feb 12, 2018

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

How can the CLI team reproduce the problem?

supporting information:

  • npm -v prints:
  • node -v prints:
  • npm config get registry prints:
  • Windows, OS X/macOS, or Linux?:
  • Network issues:
    • Geographic location where npm was run:
    • I use a proxy to connect to the npm registry.
    • I use a proxy to connect to the web.
    • I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:
    • I develop using Vagrant on Windows.
    • I develop using Vagrant on OS X or Linux.
    • I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).
@strugee
Copy link
Contributor

strugee commented Feb 12, 2018

This indicates a transient network error. Try running npm install again.

@shortthirdman
Copy link

@strugee I am also getting the same type of error (shasum check failed) since the last few days on installing any modules

@strugee
Copy link
Contributor

strugee commented Feb 21, 2018

¯_(ツ)_/¯ idk. Sounds like a duplicate of #19802. I think the registry folks would probably have to take a look at this (I'm not associated with npm)

@shortthirdman
Copy link

@strugee The npmjs registry was down due to which above problem was popping up. Now its up and running since the last week

@strugee
Copy link
Contributor

strugee commented Feb 23, 2018

Can this be closed then?

@shortthirdman
Copy link

@strugee Yes ofc

@strugee
Copy link
Contributor

strugee commented Feb 26, 2018

@shortthirdman I was actually asking OP, @Rejoyline, to get confirmation from a second person.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants