After researching various Best Practices resources, I noticed that many recommend the same project structure for Angular web applications. Websites like aglowildsolutions, tatvasoft, and even the Angular homepage all suggest using a shared module. However, I am struggling to understand the purpose of a shared module.
For example, when working with Angular Material design, I typically use around 10 material components spread across 5 feature modules. In each feature module, I end up utilizing 2 different material components. The issue arises when I have to import the entire shared module into each feature module in order to access these components. This makes me wonder if it's really any different from just having everything in either the app module or the core module.
I fail to see any clear advantage here. In fact, it seems to complicate the project structure and potentially bloat the codebase, which could ultimately impact performance negatively.