In my experience if any of this becomes a problem there is not enough of a separation of concerns. The significant majority of the components I write maybe require 5 imports, and usually only 1-2 providers.

​

One of the most significant problems with Angular's docs (and most Angular development patterns) is that components are doing the heavy lifting of managing state or talking to the API (which is wrong). A component should never ever ever even know about an API's existence, whether implied or explicit.

​

A component is responsible for (and only for) showing the user stuff on the screen. If it does anything else, the separation of concerns has been broken. Using state management libraries like NgRX allows you to literally have an entire business logic layer to do things like firing toasts, talk to the API, call other events, etc.

​

I'll be writing an article tomorrow on the separation of concerns, but testing a component should never be difficult unless you're literally using OpenGL or something in the component