Sp-dev-fx-webparts: Keep getting "Verification failed while extracting @microsoft/[email protected]"

[ZeweiS]

Category

• [x] Question
• [x] Bug
• [ ] Enhancement

When running "npm install" I am getting following error, already tried to very and clean the cache with no luck:
npm ERR! Verification failed while extracting @microsoft/[email protected]:
npm ERR! sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg= integrity checksum failed when using sha1: wanted sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg= but got sha512-SZARibyCQB+1j5b7g/6CrsUBA8pz9Yh1z+2RhXMlJcLyGkUmSriKgRmHnPjpjogQSGUAARTIFaYIMncfqL+8Pg== sha1-w6MYuEq9uEl8jKzi5LPU8hoPAII=. (1467748 bytes)

[msftbot[bot]]

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[djtrustgod]

I too have this issue . . . tarball data for @microsoft/[email protected] (sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg=) seems to be corrupted

[NPrice99]

Same here npm WARN tarball tarball data for @microsoft/[email protected] (sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg=) seems to be corrupted. Trying one more time.

[nurdena]

Same for me:
npm WARN tarball tarball data for @microsoft/[email protected] (sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg=) seems to be corrupted. Trying one more time.

[NPrice99]

Start from new machine - yo @microsoft/sharepoint - Congratulations! Solution pzl-script-editor is created. Run gulp serve to play with it! Run Gulp Serve and get this error - Error: Cannot find module '@microsoft/sp-build-web' so run npm i @microsoft/sp-build-web - get error tarball data for @microsoft/[email protected] (sha1-iImCPTaoQl6Dxjxki9BWOfq/Wwg=) seems to be corrupted

[nurdena]

Could try this solution instead for a script editor I haven't tried to deploy it yet: https://github.com/jcoleman-pcprofessional/True-Script-Editor

[NPrice99]

Hi Mikael why does the file package-lock.json in react-script-editor refer to "https://onedrive.pkgs.visualstudio.com/_packaging/odsp-npm/npm/registry" in the dependencies section rather than https://registry.npmjs.org ? Regards Nigel

[DanielJudele]

I had the same issue with @microsoft/[email protected].
I solved the issue by updating my development environment to use a higher version of the @microsoft/sp-polyfills package: nodejs version 10.17.0 (this is the working version for SharePoint Framework), Yoeman (version 3.1.0).
I deleted node_modules, the package-lock.json in the solution folder, then I run npm install.
Now I'm using @microsoft/[email protected] and seems to be fine.

[kanthvr]

hi Daniel Judele, can i have mail id. mine ramakanth.v.[email protected]

can i have .sppkg file plsss

[ZeweiS]

Got it working: modified \package-lock.json, line 874, correct value is “sha1-w6MYuEq9uEl8jKzi5LPU8hoPAII=” for "integrity". Also needed to modify name attribute, line 4, in \config\package-solution.json because "@" made the value invalid.

Owner of this project: please fix the issues as described above!

[Maya-Mostafa]

@ZeweiS thanks a lot! This fixed the issue for me :D
How did you reach this solution?

[JeanBarros]

After a long day struggling with this, @DanielJudele solution's saved me from a headache. Thank you so much for sharing.

[ravaldivia001]

@ZeweiS and @DanielJudele - combination of both solutions worked for me! Thank you so much!!!

[ChrisMenning]

Tried both of the work-arounds by @DanielJudele and @ZeweiS but am getting nowhere. Now I'm getting "PhantomJS not found on PATH" with an "ELIFCYCLE" code.

[Philzy610]

Got it working: modified \package-lock.json, line 874, correct value is “sha1-w6MYuEq9uEl8jKzi5LPU8hoPAII=” for "integrity". Also needed to modify name attribute, line 4, in \config\package-solution.json because "@" made the value invalid.
Owner of this project: please fix the issues as described above!

@ZeweiS THANK YOU! This worked.

[hugoabernier]

Hi @ZeweiS I'll mark this issue as closed as it seems that an earlier pull request may have solved this issue.

If you find that you're still experiencing the issue, feel free to re-open it.