dead-deps — what happened to your dependencies

Is @angular/http still maintained?

No — @angular/http stopped being maintained around May 2019. @angular/http's functionality was absorbed into @angular/common.

Status
No longer maintained
Last maintained
May 2019
Use instead
@angular/common on npm
Succession
Absorbed elsewhere
Drop-in
no — expect code changes
Confidence
high

What should I use instead of @angular/http?

@angular/http's functionality was absorbed into @angular/common. @angular/common is not a drop-in replacement, so expect to change call sites.

How to migrate from @angular/http to @angular/common

Import HttpClientModule from @angular/common/http and inject HttpClient. Drop the manual .json() call on responses, since HttpClient parses JSON by default.

Why @angular/http is on this list

Angular's original HTTP client was folded into @angular/common as HttpClientModule in Angular 4.3, and the standalone @angular/http package was removed in Angular 8. The npm package carries a deprecation notice pointing at @angular/common, and the v8 deprecations guide states that the entire @angular/http package has been removed. Its final release, 7.2.16, shipped in January 2020.

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

@angular/http alternatives

The dataset lists no second option: @angular/common is where the ecosystem went, and nothing else has meaningful adoption.

Check your own project for @angular/http

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

Run that in the directory holding your lockfile. If @angular/http 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.