homebridge/homebridge-config-ui-x

unable to update plugins

Scott721 opened this issue · 3 comments

Scott721 commented

Current Situation

I'm trying to update my plugins, but they both come up with the same message and don't know how to resolve the issue.
I tried reinstalling the UI and what the message said to try.

Logs

npm ERR! code EEXIST
npm ERR! syscall mkdir
npm ERR! path /Users/XXXXX/.npm/_cacache/content-v2/sha512/31/0d
npm ERR! errno EEXIST
npm ERR! Invalid response body while trying to fetch https://registry.npmjs.org/express: EACCES: permission denied, mkdir '/Users/XXXXX/.npm/_cacache/content-v2/sha512/31/0d'
npm ERR! File exists: /Users/XXXXX/.npm/_cacache/content-v2/sha512/31/0d
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

npm ERR! A complete log of this run can be found in: /Users/XXXXX/.npm/_logs/2023-11-29T03_22_51_306Z-debug-0.log


npm WARN using --force Recommended protections disabled.
npm ERR! code EEXIST
npm ERR! syscall mkdir
npm ERR! path /Users/XXXXX/.npm/_cacache/content-v2/sha512/26/3e
npm ERR! errno EEXIST
npm ERR! Invalid response body while trying to fetch https://registry.npmjs.org/homebridge-dyson-pure-cool: EACCES: permission denied, mkdir '/Users/XXXXX/.npm/_cacache/content-v2/sha512/26/3e'
npm ERR! File exists: /Users/XXXXX/.npm/_cacache/content-v2/sha512/26/3e
npm ERR! Remove the existing file and try again, or run npm
npm ERR! with --force to overwrite files recklessly.

npm ERR! A complete log of this run can be found in: /Users/XXXXX/.npm/_logs/2023-11-29T03_30_11_911Z-debug-0.log

Config

No response

Homebridge UI Version

v4.53.0

Homebridge Version

v1.7.0

Node.js Version

v20.10.0

Operating System

macOS

Environment Info

  • Using Docker?
  • Using Hyper-V?
  • Using hb-service?

Raspberry Pi Model

None

bwp91 commented

Hi @Scott721 can you try running this command in the terminal to clear the npm cache?

npm cache clean --force

and then try a plugin update again?

github-actions commented

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions commented

This issue has been closed as no further activity has occurred.