dead-deps — what happened to your dependencies

Is enzyme still maintained?

No — enzyme stopped being maintained around December 2019. The ecosystem moved to @testing-library/react, a separate project that took over the same job.

Status
No longer maintained
Last maintained
December 2019
Use instead
@testing-library/react on npm
Succession
Replacement project
Drop-in
no — expect code changes
Confidence
high

What should I use instead of enzyme?

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

How to migrate from enzyme to @testing-library/react

There is no mechanical conversion: shallow rendering and wrapper.find(...) have no direct equivalent, so tests are rewritten around render() and queries such as screen.getByRole().

Why enzyme is on this list

Enzyme's last release was 3.11.0 in December 2019, and its README states that the officially provided adapters cover React 16.x, 15.x, 0.14.x and 0.13.x only. The request for an official React 18 adapter (issue 2556) was closed without one being published, so projects on React 17 or newer have no supported adapter. The ecosystem, including the React documentation's testing guidance, moved to React Testing Library.

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

enzyme alternatives

Beyond the primary recommendation, these are credible for enzyme's use case:

Check your own project for enzyme

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

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