How to implement guide with dependency injection in angular 14: singleton services creating multiple instances
I've been banging my head against this for hours... I'm testing a new approach and I'm getting frustrated with I'm working on a project and hit a roadblock... I'm working with an scenario with dependency injection in my Angular 14 application. I have a service that is intended to be a singleton, but it appears that multiple instances are being created. This is occurring specifically when I provide this service in a lazy-loaded module. Here's the relevant part of my code: ```typescript import { Injectable } from '@angular/core'; @Injectable({ providedIn: 'root' }) export class MySingletonService { constructor() { console.log('MySingletonService instance created'); } } ``` I assume that because I provided it in the root injector, it should be a singleton throughout the app. However, in one of my lazy-loaded modules, I have the following: ```typescript @NgModule({ imports: [CommonModule], providers: [MySingletonService], // This line is causing multiple instances }) export class LazyModule {} ``` When I navigate to the lazy-loaded module, I see the console log message "MySingletonService instance created" multiple times, indicating that new instances are being created. I tried removing the `providers` array from the lazy module and only using the service in the component, but that resulted in an behavior indicating that the service couldn't be found in the injector. Is there a way to keep my service as a singleton while still being able to use it in lazy-loaded modules? Also, how can I avoid these conflicts without modifying too much of my existing structure? Any insights would be greatly appreciated! This is part of a larger service I'm building. What's the best practice here? I appreciate any insights! This is part of a larger desktop app I'm building. Thanks, I really appreciate it!