Your explanation is awesome bro. I understood the concept very well. Thanks a lot I have few queries. 1. In which scenarios do we need to choose standalone components and in which scenarios do we need to choose normal components? On what basis do we make this decision? 2. In future will Angular remove Modules completely? Modules doesn't have any advantages at all? 3. If modules are removed, how do we divide or modularize applications going forward? For example in a Healthcare related application, we create multiple modules like Patient Module, Doctor Module, Admin Module and group all the related components under each respective module. So, how do we do this kind of classification going forward?
Nice questions bro. 1. Going forward it is always good to choose standalone components. Only if your application cannot be upgraded because of any specific dependencies then you can stick to normal components. 2. There are high chances bro, because standalone components improve the performance a lot. 3. Individual standalone component itself act as a module. That is why we are importing it instead of declaring.
@@WebTechTalk Thanks a lot for your response and clarifying bro. Just have few more questions based on your response. Please don't mind so many questions from me :) 1. So, is it better to avoid modules going forward? 2. If standalone components act as modules, how do we group together or classify related components?
@@tejap7308 If your root component is going to be a standalone component, and if you are not using app module file , then it is better to avoid modules and you can maintain everything in individual standalone component. Even we can import multiple components in a standalone component. To group, we can use folders. For example, in our patient standalone component, we can import MyProfile component, MyClaim component, etc and group all components inside a single folder
in angualr 17 do we need to use the flag to have app module , or which is the optimal way here? i created app with 17 and trying to have one module for all the packages and imported this module in stand alone compoennt ie my users component , now in routing this users component is always remaining even if we route to different Route , in routeroutlet this user selectos is staying hence is always visible on ui any solution for this ?
Yes. You need to use the flag --no-standalone. But I suggest you use standalone solution. And, if you keep user component in app component, it will display in all pages. So better remove that and show it through route.
I don't think so Sai. Object oriented is the advantage of angular. Dependency injection happens through the constructor. So I think Angular will stick to class based components only.
@@WebTechTalk new way of dependency injection has come since Angular 16, and route guards also has also changed to function.that's why I'm thinking so,
