npm update check failed
See original GitHub issueHow to fix this message on every Homebridge start?
┌──────────────────────────────────────────────────────────────┐
│ npm update check failed │
│ Try running with sudo or get access │
│ to the local update config store via │
│ sudo chown -R $USER:$(id -gn $USER) /home/homebridge/.config │
└──────────────────────────────────────────────────────────────┘
if I run this command on Pi I have this chown: cannot access '/home/homebridge/.config': No such file or directory
Homebridge works as a service on my setup.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6
Top Results From Across the Web
npm update check failed - node.js - Stack Overflow
Try running the command prompt Run as administrator mode, if that not solved your issue delete the .config folder under c:\user\<name of the ......
Read more >How to resolve npm update check failed message in the terminal
How to resolve npm update check failed message in the terminal · Run the terminal with sudo or administrator role, then run an...
Read more >npm update check failed · Issue #17946 - GitHub
I'm opening this issue because: npm is crashing. npm is producing an incorrect install. npm is doing something I don't understand.
Read more >npm update check failed - Ask Ubuntu
A common case to get this error is using something like Docker (especially by mounting your own home). Consider setting the environment ...
Read more >npm-check-updates
If tests fail, restores package file and lock file. For each dependency, install upgrade and run tests. Prints broken upgrades with test error....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
npm version is - 5.0.3 I’ve also same problem when I use any npm command. npm command is working fine but why this code is showing, I don’t know…
I think it was in npm version 5.0.x issue. I updated 5.0.3 to 5.2.0 with this command
sudo chown -R $USER:$(id -gn $USER) /home/prashanth/.config
npm install -g npm now npm is working fine.
Also seeing this on a pi using systemd.