dead-deps — what happened to your dependencies

Is puppeteer-firefox still maintained?

No — puppeteer-firefox stopped being maintained around January 2020. puppeteer-firefox's functionality was absorbed into puppeteer.

Status
No longer maintained
Last maintained
January 2020
Use instead
puppeteer on npm
Succession
Absorbed elsewhere
Drop-in
no — expect code changes
Confidence
high

What should I use instead of puppeteer-firefox?

puppeteer-firefox's functionality was absorbed into puppeteer. puppeteer is not a drop-in replacement, so expect to change call sites.

How to migrate from puppeteer-firefox to puppeteer

Use puppeteer and pass browser: 'firefox' to puppeteer.launch(); a few Juggler-era APIs have no BiDi equivalent and need checking against the current Puppeteer docs.

Why puppeteer-firefox is on this list

puppeteer-firefox was an experiment that drove a patched "Juggler" build of Firefox. It is deprecated on npm, the notice records that Juggler builds stopped being available on 11 May 2023, and the last release was 0.5.1 in January 2020. Puppeteer itself now supports Firefox through WebDriver BiDi, which is enabled by default when launching Firefox, so the separate package is unnecessary.

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

puppeteer-firefox alternatives

Beyond the primary recommendation, these are credible for puppeteer-firefox's use case:

Check your own project for puppeteer-firefox

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

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