General Session
Angular's Future Without NgModules: Architectures with Standalone Components
Thanks to standalone components, Angular applications will no longer need NgModules in future. That makes them more straightforward and lightweight. While the principles behind this new feature are quickly understood, the really interesting question is: How can applications be structured without NgModules?
This question is answered here. After showing the basics and mental model of standalone components (pipes and directives), you will see several approaches for structuring your application and for grouping related building blocks. We also go into edge cases for lazy loading and the use of existing libraries based on NgModules. We discuss the interaction with tree-shakeable providers and how you can convert existing solutions step-by-step into standalone components.
By the end you know, how to improve your architectures with standalone components.
General Session
Angular's Future Without NgModules: Architectures with Standalone Components
Thanks to standalone components, Angular applications will no longer need NgModules in future. That makes them more straightforward and lightweight. While the principles behind this new feature are quickly understood, the really interesting question is: How can applications be structured without NgModules?
This question is answered here. After showing the basics and mental model of standalone components (pipes and directives), you will see several approaches for structuring your application and for grouping related building blocks. We also go into edge cases for lazy loading and the use of existing libraries based on NgModules. We discuss the interaction with tree-shakeable providers and how you can convert existing solutions step-by-step into standalone components.
By the end you know, how to improve your architectures with standalone components.