Integrity Integrity Error When Installing Connect API Toolkit #apiconnect

When installing the Connect API, the following error appears:

sha1-UhOHSxsj + deaxi0QbjKXDirzcn8 = integrity checksum failed when using sha1: wanted sha1-UhOHSxsj + deaxi0QbjKXDirzcn8 = but got sha1-208ds / bfbkHrcce1kMfz2sUP. (627039 bytes)

Node version: - 6.10.3 NPM version: - 5.0.1

I am trying to install the Connect API on a Windows 7 workstation (64-bit) using the npm install -g apiconnect command.

What could be the following steps to resolve this issue?

+12
source share
9 answers

I ran into this problem, fortunately I found a solution on Github :

this is called package-lock.json ,

so i delete it: rm package-lock.json

enter image description here

then i run npm install it works for me.

+16
source

I got a similar error in Node (v8.1.0) and NPM (5.0.3) versions on Windows 10. After fixing this problem, follow these steps. a) Utility npm and Node.js completely. b) Delete the "npm" and "npm-cache" folders from the location "C: \ Users \\ AppData \ Roaming". c) Install the latest version of node via ".msi" d) from node launch the command line "npm i -g npm" e) go to the place of your project and run "npm install", it should work.

+4
source

I was getting the same issue too, but solved

(1st get old version of npm 4.xx)

 npm install -g npm@4.6.1 

The following is optional in your case, if you are building something and there is package.lock.json in your project, remove package.lock.json (this means that version 5 of the node is installed, as some installers (for example, when deploying the application to Heroku application) automatically detect this file and upgrade to version 5)

Now try npm install, it should work

thanks

+3
source

This should help you:

Simple soul:

 sudo npm i npm@latest -g 
0
source

There are several solutions to this problem. I have come across this many times, and different things have always helped me.

A. First try flushing the cache: flushing the cache npm cache clean --force then npm install

B. Secondly, you can try npm install --update-binary

C. Third option is to try A and delete the node_modules folder and then npm install

D. The fourth option is to remove nodejs, reboot and reinstall, and then try npm install

E. The last of my options that worked for me was to delete the npm and npm-cache folders in Users%username%\AppData\Roaming and run npm install

You can try other combinations, it is usually better to always do A and at least clear the cache or delete the node_modules folder.

0
source

Starting with npm 5, you can use npm-cache to check the contents of the cache folder, for example:

 npm cache verify 

Then run install again.

0
source

Go to the dir directory and enter the following commands in fx powershell or cmd.

 rm ./package-lock.json npm cache clear --force npm install -g npm 

It worked for me.

0
source

try again, add params '--unsafe-perm = true' npm install -g plugman --unsafe-perm=true

-1
source
 yarn install 

worked for a similar error. check here

-3
source

Source: https://habr.com/ru/post/1268478/


All Articles