dead-deps — what happened to your dependencies

Is uglifyjs-webpack-plugin still maintained?

No — uglifyjs-webpack-plugin stopped being maintained around July 2019. uglifyjs-webpack-plugin's own maintainers named terser-webpack-plugin as the successor.

Status
No longer maintained
Last maintained
July 2019
Use instead
terser-webpack-plugin on npm
Succession
Successor named by the maintainers
Drop-in
no — expect code changes
Confidence
high

What should I use instead of uglifyjs-webpack-plugin?

uglifyjs-webpack-plugin's own maintainers named terser-webpack-plugin as the successor. terser-webpack-plugin is not a drop-in replacement, so expect to change call sites.

How to migrate from uglifyjs-webpack-plugin to terser-webpack-plugin

On webpack 5 you can usually delete the plugin entirely, since production mode minifies by default; if you need custom options, configure optimization.minimizer with terser-webpack-plugin.

Why uglifyjs-webpack-plugin is on this list

webpack-contrib archived uglifyjs-webpack-plugin in December 2019, and the README's notice points at terser-webpack-plugin. The last release was 2.2.0 in July 2019 and the plugin only ever supported webpack 4. webpack 5 minifies with Terser in production mode without any plugin entry of your own; note the maintained plugin is now also published under the name minimizer-webpack-plugin.

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

uglifyjs-webpack-plugin alternatives

Beyond the primary recommendation, these are credible for uglifyjs-webpack-plugin's use case:

Check your own project for uglifyjs-webpack-plugin

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

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