Is react-testing-library still maintained?
No — react-testing-library stopped being maintained around May 2019. The same project continues under the name @testing-library/react.
- Status
- No longer maintained
- Last maintained
- May 2019
- Use instead
@testing-library/react— on npm- Succession
- Renamed package
- Drop-in
- yes — swap the import
- Confidence
- high
What should I use instead of react-testing-library?
The same project continues under the name @testing-library/react. @testing-library/react is close enough to a drop-in replacement that most projects only change the dependency and the import.
How to migrate from react-testing-library to @testing-library/react
Swap the dependency and update imports to @testing-library/react; the exported render, screen and query helpers kept their names.
Why react-testing-library is on this list
The Testing Library family was consolidated under the @testing-library scope in 2019. The unscoped react-testing-library package carries an npm notice asking users to uninstall it and install @testing-library/react instead, with the reasoning recorded in dom-testing-library issue 260. The sibling package dom-testing-library moved to @testing-library/dom in the same change.
The succession is settled: primary sources agree and the ecosystem has already moved.
react-testing-library alternatives
The dataset lists no second option: @testing-library/react is where the ecosystem went, and nothing else has meaningful adoption.
Check your own project for react-testing-library
npx dead-deps --all --min-state unmaintainedRun that in the directory holding your lockfile. If react-testing-library 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:
- npm deprecation notice on react-testing-librarynpmjs.com
- dom-testing-library issue 260: Create @testing-library scope for publishinggithub.com
Packages related to react-testing-library
- enzymeReplacement project: @testing-library/react · unmaintained since December 2019
- react-addons-test-utilsAbsorbed elsewhere: react-dom · unmaintained since April 2017
- create-react-appSuccessor named by the maintainers: vite · unmaintained since February 2025
- hapiRenamed package: @hapi/hapi · unmaintained since February 2019
- labRenamed package: @hapi/lab · unmaintained since February 2019
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.