npm update check failed — Try running with sudo or get access to the local update config store
npm’s update notifier couldn’t write its config — usually root-owned files in ~/.config from a past sudo npm.
Seen on:
npm
Meaning
Harmless for installs, but shows ownership problems in your home directory.
Common causes
- ~/.config owned by root after sudo npm
- Home directory mounted read-only in CI/containers
⚡ Quick fix
- sudo chown -R $USER:$(id -gn $USER) ~/.config
- Disable the notifier: npm config set update-notifier false
Detailed fix by platform
Linux
sudo chown -R $USER:$(id -gn $USER) ~/.config ~/.npm
How to diagnose
- Owner — ls -la ~/.config
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026