dead-deps — what happened to your dependencies

Is request-promise-any still maintained?

No — request-promise-any stopped being maintained around July 2020. The ecosystem moved to got, a separate project that took over the same job.

Status
No longer maintained
Last maintained
July 2020
Use instead
got on npm
Succession
Replacement project
Drop-in
no — expect code changes
Confidence
high

What should I use instead of request-promise-any?

The ecosystem moved to got, a separate project that took over the same job. got is not a drop-in replacement, so expect to change call sites.

How to migrate from request-promise-any to got

Drop the pluggable-promise layer entirely and call got, which returns native promises; any remaining Bluebird-specific helpers can be replaced with Promise.all or p-map.

Why request-promise-any is on this list

request-promise-any let callers plug in any Promises/A+ implementation on top of request via the any-promise module, and it was deprecated in July 2020 with the rest of the request family. The npm notice cites the deprecation of the underlying request package. A pluggable promise layer is rarely needed now that native promises are universal.

The succession is settled: primary sources agree and the ecosystem has already moved.

request-promise-any alternatives

Beyond the primary recommendation, these are credible for request-promise-any's use case:

Check your own project for request-promise-any

npx dead-deps --all --min-state unmaintained

Run that in the directory holding your lockfile. If request-promise-any is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.

Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.

Evidence

Every claim on this page traces to a primary source. Check them:

See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.