dead-deps — what happened to your dependencies

Is eslint-loader still maintained?

No — eslint-loader stopped being maintained around April 2020. eslint-loader's own maintainers named eslint-webpack-plugin as the successor.

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

What should I use instead of eslint-loader?

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

How to migrate from eslint-loader to eslint-webpack-plugin

Delete the loader rule and add new ESLintPlugin({ extensions: ['js','jsx','ts','tsx'] }) to plugins. Loader options such as fix and failOnError map onto plugin options of the same name.

Why eslint-loader is on this list

webpack-contrib deprecated eslint-loader in favour of eslint-webpack-plugin, and the npm notice says so directly. Running the linter as a plugin instead of a loader lets it check files webpack never resolves and avoids re-linting on every module build. The loader's last release was 4.0.2 in April 2020.

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

eslint-loader alternatives

The dataset lists no second option: eslint-webpack-plugin is where the ecosystem went, and nothing else has meaningful adoption.

Check your own project for eslint-loader

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

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