Should I create a module per component in Angular 4+ app? : <p>We have a medium sized Angular 4 application (+-150 components).</p>

<p>Many of these components require the injection of service classes and require the declaration of other components in the app.</p>

<p>An approach we have been experimenting with, and have found to be much more developer friendly, is to create a module per component. The module imports the child component modules and provides (or imports) all the services needed by the component. It also exports the component itself so that other components can reference it through the module.</p>

<p>It makes the composition of components a breeze and the setup of the test fixture of a component very simple (this is where there was previously a lot of repetition of dependencies and child component tree dependencies).<br>
This approach seems to match the component based architecture and allows for a form of encapsulation around what a components dependencies are.<br>
It feels just too good to be true ;)</p>

<p>My question is, what is the performance (or other) impact of having so many modules?</p>
