dead-deps — what happened to your dependencies

Is supertest-as-promised still maintained?

No — supertest-as-promised stopped being maintained around November 2016. supertest-as-promised's functionality was absorbed into supertest.

Status
No longer maintained
Last maintained
November 2016
Use instead
supertest on npm
Succession
Absorbed elsewhere
Drop-in
yes — swap the import
Confidence
high

What should I use instead of supertest-as-promised?

supertest-as-promised's functionality was absorbed into supertest. supertest is close enough to a drop-in replacement that most projects only change the dependency and the import.

How to migrate from supertest-as-promised to supertest

Delete the dependency and call supertest(app) directly; .expect(...) already returns a thenable, so existing .then() chains keep working.

Why supertest-as-promised is on this list

This package existed only to add promise support to SuperTest. SuperTest 2.0 made its request objects thenable natively, and the wrapper carries an npm notice saying to use SuperTest directly. The repository is archived and the last release was 4.0.2 in November 2016.

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

supertest-as-promised alternatives

The dataset lists no second option: supertest is where the ecosystem went, and nothing else has meaningful adoption.

Check your own project for supertest-as-promised

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

Run that in the directory holding your lockfile. If supertest-as-promised 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.