npm WARN deprecated package@1.2.3: This package is no longer supported.
A dependency (often a transitive one) is deprecated by its author.
npm WARN deprecatedis no longer supported Meaning
Warnings, not errors. Many come from deep dependencies you don’t control (glob, inflight, rimraf). Upgrade direct dependencies to pull in newer versions.
Common causes
- Old direct dependency
- Transitive dependency of an outdated package
- Package abandoned by its maintainer
⚡ Quick fix
- Find who pulls it in: npm ls package
- Upgrade the parent package
- Use overrides only when safe
Detailed fix by platform
npm
npm ls inflight
How to diagnose
- Source — Direct or transitive?
- 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:
Similar errors
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 12 Oct 2026