Reading about standalone components for the first time today and I don't need to see another video I think. Very nicely explained bro. Keep up the good work. :)
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,
even better than the official video talking about standalone component
Thank you so much
Reading about standalone components for the first time today and I don't need to see another video I think. Very nicely explained bro. Keep up the good work. :)
Thank you so much 👍
Excellent video covers lot of items in single video
Thank you
To the point, compact , useful and full of knowledge. Thanks for the sharing this ..
Thank you so much.
Very neat and clear explanation, thank you
Thanks a lot
Excellent explanation. I understood the concept very well. thanks, keep it up
Thank you so much 🙏
I love the way you demonstrate lazy loading. thanks
Thank you so much
Best example. To the point and covered all. Thanks.
Thank you so much.
Great Explanation!
@@amgadmohammed6358 Thank you 🙏
@@amgadmohammed6358 Thank you 🙏
Excellent topic❤ sir i understand very well bcz of this topic video i got stuck before this video now cleared the topic🥳
Nice to hear that. Thank you so much.
Very Good explanation 🎉 I can understand easily. Keep it up.. congratulations for 10K Subscribers 🎉😊
Thank you so much 😀
Really good context and covered in very short video. Kudos to you. Keep it up👍
Thank you so much bro.
Very well explained thanks, keep it up❤
Thank you bro 😊
Wonderful Series ...Bless You
Thank you so much 🙏
Superb video ❤
Thanks 🤗
Best explanation, thank you!
@@psteja9917 Thank you
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
@@WebTechTalkThanks a lot for clarifying bro. Your channel is best I have seen for Angular so far. Excited to see more Angular videos from you 😊
@@tejap7308 Thank you so much bro 😄
awesome, really appreciate, thx a lot
Thank you so much
Best one. For.. New learners
Thank you bro.
Well explained
Thank you 🙏
Great video.
Thanks.
Thank you
Now I understand thank you!
Thank you 🙏
Take a look also to Local Change Detection
Sure. I am planning to cover this after doing a video on Signals.
awesome explanation
Thank you so much 👍
Nice explanation and very useful
Thank you so much
thank you greate explain
Thank you 👍
well explained!!
Thanks
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.
It seems angular may slowly convert to function based components as similar to react
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,
@@SaiKumar-tg6ct I will explore more on that
👍
Thanks
content is good but background music is noising
OK, I will reduce the noise.