Why Do We Need `provideHttpClient()` Instead of `new HttpClient()`?

When you first start learning Angular, one question almost everyone asks is:

Why can’t I simply write const http = new HttpClient();?

Instead, Angular asks us to use provideHttpClient(). Let’s understand why with a simple analogy.

Imagine You’re Building a House

Every room needs electricity. Instead of hiring a separate electrician for every room, the builder installs one main electrical system that every room uses.

Programming Has the Same Problem

If every Angular service creates its own HttpClient, the same setup work is repeated over and over.

export class UserService {
  http = new HttpClient();
}

This leads to duplicated code and makes maintenance harder.

What Does Angular Do?

Angular says: “Don’t create your own HttpClient. I’ll create one and share it across the application.”

bootstrapApplication(AppComponent, {
  providers: [provideHttpClient()]
});

How Services Use It

constructor(private http: HttpClient) {}

Your service simply asks Angular for an HttpClient, and Angular provides the already configured instance.

Why Is This Better?

One shared HttpClient
Less duplicate code
Easier testing
Centralized authentication, logging, retries and error handling
Easier maintenance as the application grows

Real-Life Example

Think about your home Wi-Fi. You don’t buy a separate internet connection for every device. One router serves your phone, laptop, TV, and tablet. provideHttpClient() works exactly the same way.

Final Thoughts

provideHttpClient() helps Angular create one well-configured HttpClient that every service can share. Instead of every service building its own, Angular provides one reliable, reusable instance for the entire application.

Why Do We Need provideHttpClient() Instead of new HttpClient()?