@angelfraga9907

I really appreciate your work here. nice talk. Well paused, step by step, just awesome. Thanks Rainer!

@ИванКудря-ь3ш

Hy. I am 24 and I stacked between middle and senior position. Videos like this can help to get some data about app architecture, with is gold now. This video is very helpful and gives a good start point. Please keep sharing you knowledge.
Thank you so much!

@mehr8248

Really enjoyed this video and understood the concepts. Thanks so much!

@claudiuciprianbetiuc3985

High quality presentation ! Thank you, Rainer !

@hansschenker

An Angular module is a unit of angular compilation - it is necessary for the Angular compiler! It is hardly to imagine that this will ever go away.
An Angular module is also a perfect unit for a feature module. A feature module contains all components, state this feature is in need of and is located in its own folder:
products
   module
  components
    page (container comp)
    list (presentation comp)
    view (presentation com)
state (products state - models)
  service (products service provided by products module)

N/A

The title of this video is misleading. The first mention of Standalone Components is at 22:00 out of a 24:00 video. No code is shown about them. This video is more about NX architecture than anything else.

@oskar42314

These are great. Thank you.

@MarkusThiel

I might be missing something here but you state that if we are using libraries we are on the right track.. but the libraries does also contain modules? isn't the point to get rid of these modules that holds components?

@vmedinsky

Great explanation! Keep going! :)

@huantao2274

I like your explanation regarding nx projects as the real "module" that can be shared between apps. What if App A and App B both need share an nx lib C, BUT, A and B are not in the same code base? How do I do with the shareable C? Package it to a real library and host it?

@MrNix2012

Great talk, thx for that :). It was quite interesting. One/two questions I have. Is webpack smart enough to handle duplicate imports? I mean, what will happen, when I have 2 different components but both are using somehow similar exported stuff like models or services? They will not exist twice, right? When I use both components in one component, or?

@hansschenker

scam is a good idea but not very practical!