Angular by default creates a single isntance for the entire application but you can configure individual modules to have an additional instance exclusive to that module. Further, a service can exist within a scope that isn't the application scope. While you may not need any of these edge cases, you can easily achieve the entire dependency injection system that Angular has with TSyringe.
Angular by default creates a single isntance for the entire application but you can configure individual modules to have an additional instance exclusive to that module. Further, a service can exist within a scope that isn't the application scope. While you may not need any of these edge cases, you can easily achieve the entire dependency injection system that Angular has with TSyringe.
Totally agree, I simplified my post and goal by saying "per default a service exists once".
Thank you for the nice add-ons 👍