npm WARN deprecated request@2.88.2: request has been deprecated
npm WARN deprecated uuid@3.4.0: Please upgrade to v7 or higher

A package you depend on (directly or indirectly) is deprecated — the maintainer marked it as no longer maintained or replaced by something better.

When to worry

Don’t worry if: it’s a sub-dependency (a dependency of a dependency). You can’t control it directly, and it usually still works fine.

Do worry if: it’s a direct dependency in your package.json, especially if it has known security vulnerabilities.

Fix 1: Update the package

# Check if a newer, non-deprecated version exists
npm outdated

# Update a specific package
npm install uuid@latest

# Update everything
npm update

Fix 2: Find a replacement

If the package is truly abandoned, find an alternative:

# Check the npm page for the package — it often suggests a replacement
npm info request

# Common replacements:
# request → axios, node-fetch, or built-in fetch (Node 18+)
# moment → dayjs, date-fns
# uuid@3 → uuid@9

Fix 3: It’s a sub-dependency (you can’t control it)

# Check who depends on the deprecated package
npm ls request

# If it's deep in the tree, the parent package needs to update
# You can try overriding it in package.json:

{
  "overrides": {
    "request": "npm:postman-request@2.88.1-postman.33"
  }
}

Fix 4: Suppress the warnings (not recommended)

npm install --no-warnings

This hides all warnings, not just deprecation ones. Not recommended — you might miss important warnings.

The reality

Most deprecation warnings are harmless noise from sub-dependencies. Focus on your direct dependencies being up to date and secure. Run npm audit to check for actual security issues.

See also: npm cheat sheet | npm peer dependency error fix