Is jest-environment-jsdom-sixteen still maintained?
No — jest-environment-jsdom-sixteen stopped being maintained around April 2021. jest-environment-jsdom-sixteen's functionality was absorbed into jest-environment-jsdom.
- Status
- No longer maintained
- Last maintained
- April 2021
- Use instead
jest-environment-jsdom— on npm- Succession
- Absorbed elsewhere
- Drop-in
- yes — swap the import
- Confidence
- high
What should I use instead of jest-environment-jsdom-sixteen?
jest-environment-jsdom-sixteen's functionality was absorbed into jest-environment-jsdom. jest-environment-jsdom is close enough to a drop-in replacement that most projects only change the dependency and the import.
How to migrate from jest-environment-jsdom-sixteen to jest-environment-jsdom
Remove the dependency and set testEnvironment: 'jsdom' in the Jest config; on Jest 28 and later also install jest-environment-jsdom, which is no longer bundled with Jest.
Why jest-environment-jsdom-sixteen is on this list
This package existed to give older Jest versions a jsdom 16 environment. It carries an npm notice saying Jest 26 ships jsdom 16 so there is no reason to use it, and its last release was 2.0.0 in April 2021. From Jest 28 onward the jsdom environment is published by the Jest team as jest-environment-jsdom.
The succession is settled: primary sources agree and the ecosystem has already moved.
jest-environment-jsdom-sixteen alternatives
The dataset lists no second option: jest-environment-jsdom is where the ecosystem went, and nothing else has meaningful adoption.
Check your own project for jest-environment-jsdom-sixteen
npx dead-deps --all --min-state unmaintainedRun that in the directory holding your lockfile. If jest-environment-jsdom-sixteen 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 jest-environment-jsdom-sixteen ("jest@26 ships with jsdom@16")npmjs.com
- npm: jest-environment-jsdom, maintained by the Jest teamnpmjs.com
Packages related to jest-environment-jsdom-sixteen
- @angular/httpAbsorbed elsewhere: @angular/common · unmaintained since May 2019
- @zeit/next-sassAbsorbed elsewhere: next · unmaintained since March 2020
- puppeteer-firefoxAbsorbed elsewhere: puppeteer · unmaintained since January 2020
- querystringReplaced by URLSearchParams in the platform · unmaintained since February 2021
- react-addons-test-utilsAbsorbed elsewhere: react-dom · unmaintained since April 2017
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.