search

catalogicsoftware / ngx-dynamic-dashboard-framework

This is a JSON driven angular x based dashboard framework that is inspired by JIRA's dashboard implementation and https://github.com/raulgomis/angular-dashboard-framework
MIT License
187 stars 95 forks source link

npm install issues #13

Open praveenrajjogi opened 5 years ago

praveenrajjogi commented 5 years ago

Hi , When i try to clone and install the project am facing the various below errors

1.npm ERR! code EINTEGRITY npm ERR! sha1-mnHEh0chjrylHlGmbaaCA4zct78= integrity checksum failed when using sha1: wanted sha1-mnHEh0chjrylHlGmbaaCA4zct78= but got sha1-krNyb8WyKnkXwdvJF2zG uZcSuXI=. (10681087 bytes)

2.audited 31272 packages in 30.275s found 77 vulnerabilities (33 low, 26 moderate, 18 high) run npm audit fix to fix them, or npm audit for details

3.npm WARN tarball tarball data for material-design-icons@3.0.1 (sha1-mnHEh0chjrylHlGmbaaCA4zct78=) seems to be corrupted. Trying one more time. npm ERR! path D:\dashboard\ngx-dynamic-dashboard-framework-master\node_modules.staging\material-design-icons-50593f6c\editor\ios\ic_monetization_on_36pt.imageset\ic_monetization_on_36pt_3x.png npm ERR! code EPERM npm ERR! errno -4048 npm ERR! syscall unlink npm ERR! Error: EPERM: operation not permitted, unlink 'D:\dashboard\ngx-dynamic-dashboard-framework-master\node_modules.staging\material-design-icons-50593f6c\editor\ios\ic_monetization_on_36pt.imageset\ic_monetization_on_36pt_3x.png'

so please help me out in figuring it

jayhamilton commented 5 years ago

I will take a look to see if I can reproduce the problem.

jayhamilton commented 5 years ago

@praveenrajjogi for number

  1. Could not reproduce this. That said, see the following stack over flow issue: https://stackoverflow.com/questions/47545940/npm-err-code-eintegrity-npm-5-3-0 In addition to that try updating to the latest version of npm

  2. I just checked in updates to the package.json after running npm audit to remove many of the vulnerabilities. However, more are pending with Semantic-UI as related to gulp. I believe they are working on fixes now.

  3. Could not reproduce this either. Will review more.

Did you run npm install on the checked out repository or did you see these issues as a result of running the build.sh script?