npm error while installing npm

[sabarinathen]

[ERROR] An error occurred while running npm install (exit code 1):

        npm WARN deprecated babili@0.1.2: babili has been renamed to babel-minify. Please update to babel-minify
        npm WARN deprecated babel-preset-babili@0.1.4: babili has been renamed to babel-minify. Please update to
        babel-preset-minify
        npm WARN deprecated object-keys@0.2.0: Please update to the latest object-keys
        npm WARN ajv-keywords@2.1.0 requires a peer of ajv@>=5.0.0 but none was installed.
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: core-js@2.5.1 (node_modules\core-js):
        npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, open
        'C:\Users\Admin\appsam3\node_modules\.staging\core-js-75f56269\fn\typed\int16-array.js'
        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.2 (node_modules\fsevents):
        npm WARN enoent SKIPPING OPTIONAL DEPENDENCY: ENOENT: no such file or directory, open
        'C:\Users\Admin\appsam3\node_modules\.staging\fsevents-2318abf5\node_modules\balanced-match\LICENSE.md'

        npm ERR! code EINTEGRITY
        npm ERR! sha512-BEMB+WhtpTZCnBA6t+TMtfZaukcqNS5zlTAV53s+U92p+6Hg6BLVzmOvxqm0tA/TSfwXNFtQ08lxS8uMFUxivA==
        integrity checksum failed when using sha512: wanted
        sha512-BEMB+WhtpTZCnBA6t+TMtfZaukcqNS5zlTAV53s+U92p+6Hg6BLVzmOvxqm0tA/TSfwXNFtQ08lxS8uMFUxivA== but got
        sha512-gHxMNVQ6aJCHXRXiktmqJQ2cwxRN8pYoyDC2r0iHL3uat/iBtU3XO64wZ3xD1t3YNMaCnC4h3ET35JNMcGld2w==. (409600 bytes)

[groax]

I have the same error.... How to fix this?

[zhaoshiming]

i got this error too. and i delete the node_modules file and run npm install myselft,but it does not work .it seems like it a proxy error.

[jakeNiemiec]

Same here, @kenany when can we get a meta-issue for all the EINTEGRITY issues?
https://github.com/npm/npm/search?o=desc&q=EINTEGRITY&type=Issues

[kenany]

Hmm, that wouldn't be a bad idea :)

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.