Common causes
- The package maintainer added a deprecation notice to the npm registry
- A transitive dependency (a dependency of your dependency) is deprecated
- You're installing an old version of a package that has been superseded
- The package was abandoned and a different package is now the recommended replacement
How to fix it
- Check the deprecation message — it usually suggests a replacement package
- Search for the recommended alternative and migrate to it
- If it's a transitive dependency, check if upgrading the parent package fixes it
- For now, the package usually still works — treat this as a future migration task
Example
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142Installing a package that depends on the deprecated 'request' HTTP library
Have a different error?
Paste any error message into the Error Translator to get an instant explanation.
