Explain provider scope.
Skip to solutionKEEP THE
mediumFrontend
What is the difference between providing a service in root vs in a component?
288 views
01
Understand the problem
diprovidedin
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
providedIn: 'root' (or providing at the app level) creates one singleton shared everywhere. Providing a service in a component's providers array creates a new instance per component instance (and its children) — useful for component-scoped state that shouldn't be shared.
Solution ready — 2 min read
Classified // press E to declassify
04
Read the code
Root singleton vs component-scoped
import { Component, Injectable } from '@angular/core';
@Injectable({ providedIn: 'root' }) // ONE shared instance app-wide
export class GlobalCart {}
@Injectable() // not auto-provided
export class WidgetState {}
@Component({
selector: 'app-widget',
standalone: true,
providers: [WidgetState], // NEW WidgetState per <app-widget>
template: '...',
})
export class WidgetComponent {
// each <app-widget> gets its own WidgetState;
// GlobalCart is the same instance everywhere.
}05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 72 of 121 decoded in the Angular track. One more won't hurt.