Suggest an editImprove this articleRefine the answer for “How does DI work in standalone components?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)In standalone components, DI (Dependency Injection) works the same way as in regular ones, just without an NgModule: each component has its own injector, and if a dependency is not found locally, Angular goes up to the root injector. **Key point:** Dependency lookup goes from the component's `providers` to parent components and then to the root of the application.Shown above the full answer for quick recall.Answer (EN)ImageIn standalone components, Angular's DI (Dependency Injection) system works the same way as in regular ones, just **without a module**. The main points: - A component has **its own injector**, created when it is initialized. - Dependencies can be declared in `providers` right inside `@Component()`. They are **available only to that component and its descendants**. - If a dependency is not found in the local injector, Angular goes up, to the **root injector**, where services marked `@Injectable({ providedIn: 'root' })` live. That is: 1. First it looks in the component's `providers`, 2. then in the parent components, 3. then at the root of the application. DI stays the same, the hierarchy is just built without an NgModule.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.