npm update check failed npm Origin: Build & delivery OSI layer 7 · Application Last updated 13 Oct 2026

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.

Exact message you may see npm update check failedlocal update config store
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

  1. sudo chown -R $USER:$(id -gn $USER) ~/.config
  2. Disable the notifier: npm config set update-notifier false

Detailed fix by platform

Linux

  1. sudo chown -R $USER:$(id -gn $USER) ~/.config ~/.npm

How to diagnose

  1. Owner — ls -la ~/.config
  2. Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

AADSTS65001 — AADSTS65001: The user or administrator has not consented to use the application (Azure)AADSTS65001AADSTS90002 — AADSTS90002: Tenant 'x' not found (Azure)AADSTS90002AccessControlListNotSupported — AccessControlListNotSupported: The bucket does not allow ACLs (AWS)AccessControlListNotS…api_version_invalid — API Error: Invalid or unsupported API version (API)api_version_invalidConnectionString property has not been initialized — InvalidOperationException: The ConnectionString property has not been initialized (.NET)ConnectionString prop…daemon — Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? (Docker)daemondivergent branches — hint: You have divergent branches and need to specify how to reconcile them. (Git)divergent branchesDocker Desktop requires privileged access (vmnetd) — macOS: Docker Desktop needs privileged access / com.docker.vmnetd could not be started (macOS)Docker Desktop requir…npm updat…

Explore the map of this error Full error map →

🧠 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.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.