I see more and more people adopting the Single-Component-As-Module approach. What do you all think about maybe adding some --as-module flag when generating new component, directive or pipe? It's a hot topic, it dramatically decrease bundle size and resolve the shared/core-shared struggle on large projects.
Describe the solution you'd like
Extend current ng generate behaviour with a flag to generate new component / directive / pipe wrapped into a single module. It wouldn't introduce any breaking changes and is profitable if you care about architecture & of course, performance.
Describe alternatives you've considered
It's ok to do it manually though it would be a valuable shortcut.
If I can PR that?
YES!
The text was updated successfully, but these errors were encountered:
Command (mark with an
x)Description
I see more and more people adopting the Single-Component-As-Module approach. What do you all think about maybe adding some
--as-moduleflag when generating new component, directive or pipe? It's a hot topic, it dramatically decrease bundle size and resolve the shared/core-shared struggle on large projects.Describe the solution you'd like
Extend current
ng generatebehaviour with a flag to generate new component / directive / pipe wrapped into a single module. It wouldn't introduce any breaking changes and is profitable if you care about architecture & of course, performance.Describe alternatives you've considered
It's ok to do it manually though it would be a valuable shortcut.
If I can PR that?
The text was updated successfully, but these errors were encountered: