Material-design-icons: npm WARN tarball tarball data for material-design-icons@^3.0.1 (sha1-mnHEh0chjrylHlGmbaaCA4zct78=) seems to be corrupted. Trying one more time.

[prakashsellathurai]

[jestelle]

Any luck? I'm not sure we'll be able to help with this any time soon.

[prakashsellathurai]

nope npm could't install material design icons locally

[llorenspujol]

same here, someone knows if there a way to fix this?

[SSP16SCM59S]

npm WARN tarball tarball data for [email protected] (sha1-mnHEh0chjrylHlGmbaaCA4zct78=) seems to be corrupted. Trying one more time.
npm ERR! path C:\Users\sshankaranand\workspace\ngDesk-WebAppnode_modules.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png
npm ERR! code EPERM
npm ERR! errno -4048
npm ERR! syscall unlink
npm ERR! Error: EPERM: operation not permitted, unlink 'C:\Users\sshankaranand\workspace\ngDesk-WebAppnode_modules.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png'
npm ERR! { [Error: EPERM: operation not permitted, unlink 'C:\Users\sshankaranand\workspace\ngDesk-WebAppnode_modules.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png']
npm ERR! cause:
npm ERR! { Error: EPERM: operation not permitted, unlink 'C:\Users\sshankaranand\workspace\ngDesk-WebAppnode_modules.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png'
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path:
npm ERR! 'C:\Users\sshankaranand\workspace\ngDesk-WebApp\node_modules\.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png' },
npm ERR! stack:
npm ERR! 'Error: EPERM: operation not permitted, unlink \'C:\Users\sshankaranand\workspace\ngDesk-WebApp\node_modules\.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png\'',
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'unlink',
npm ERR! path:
npm ERR! 'C:\Users\sshankaranand\workspace\ngDesk-WebApp\node_modules\.staging\material-design-icons-8bb3f075\hardware\drawable-xxxhdpi\ic_computer_white_36dp.png',
npm ERR! parent: 'ng-desk-web-app' }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator (though this is not recommended).

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\sshankaranand\AppData\Roaming\npm-cache_logs\2018-10-02T17_24_47_870Z-debug.log

[SSP16SCM59S]

same issue those are my logs

[PrajwalMathad]

Facing the same issue. npm is failing to install material-design-icons.
npm WARN tarball tarball data for [email protected] (sha1-mnHEh0chjrylHlGmbaaCA4zct78=) seems to be corrupted. Trying one more time.

[sebagra]

After many days of troubleshooting, I got this fixed by removing the node_modules folder and running an npm update.
https://stackoverflow.com/questions/52739973/npm-tarball-data-for-material-design-icons-seems-to-be-corrupted

[PrajwalMathad]

After many days of troubleshooting, I got this fixed by removing the node_modules folder and running an npm update.
https://stackoverflow.com/questions/52739973/npm-tarball-data-for-material-design-icons-seems-to-be-corrupted

Thank you @sebagra . This works fine.

[gforceg]

This didn't happen to me but it happened to my build agent. Both the agent and I use a nexus npm registry rather than npmjs.com. Running npm cache verify solved the issue.

Does anyone know what the root cause was?

[839998664]

I have tried npm vache verify as well as the solutions provided at the stack overflow URL. Still getting the same error. It's been over 6 days of trying different things. Failed at a technical screening round for a job because of this one.

[MystereC]

I have the same problem ! since i did git clone . i did every solution! npm cache verify , deleted node_module , npm install . since 1 week i'm stuck

[839998664]

I have tried npm vache verify as well as the solutions provided at the stack overflow URL. Still getting the same error. It's been over 6 days of trying different things. Failed at a technical screening round for a job because of this one.

...Update on this, finally worked for me...I was trying all the steps from within Visual Studio Code IDE Powershell console...Opened a command prompt (Run as Administrator) instead...Ran npm install...worked in single go...Tried this since I faced similar issue with another package in another project as well...

[ThetaSinner]

@839998664 I've just tried your suggestion. I'm using nexus as a proxy for the npm registry. Removing the package from the nexus proxy, deleting my npm cache then running the install from cmd worked for me.

[patrick-yi-82]

I logged in to thank you.
This worked.

npm update
npm install

[KEMBL]

Worked for me:
yarn install

[bdrazen]

I have the same problem ! since i did git clone . i did every solution! npm cache verify , deleted node_module , npm install . since 1 week i'm stuck

@MystereC In the same boat as you (none of these solutions have worked for me). Did you ever solve it? Thanks.

[mpecro]

I solved this issue by removing the library from the dependencies...

[anuj9939]

I have tried npm vache verify as well as the solutions provided at the stack overflow URL. Still getting the same error. It's been over 6 days of trying different things. Failed at a technical screening round for a job because of this one.

...Update on this, finally worked for me...I was trying all the steps from within Visual Studio Code IDE Powershell console...Opened a command prompt (Run as Administrator) instead...Ran npm install...worked in single go...Tried this since I faced similar issue with another package in another project as well...

this work for me too

[Toomavic]

My Environment:

node --version
v10.17.0

npm --version
6.11.3

I tried the following:

• remove node_modules.
• then run npm updtae
• then npm i

This solved my problem ✔️

[pacocom]

rm -rf node_modules
npm update
npm i

Not working for me!

$ node -v
v12.3.1
$ npm --version
6.9.0