Angular Standalone Components - No Ngmodules Anymore 

Glad it helped!

Thank you!

I rerecord the whole angular ngrx course with standalone components and the amount of code is 30% smaller for sure.

Much appreciated!

Glad it was helpful!

This is a new way of Angular. Now they say that ngModules are optional which means it will soon transition to standalone like it was with hooks inside React

@@MonsterlessonsAcademy thanks this is very interesting

Good to know!

basic on your experience - is application with ngModules or without more readable?

I like it more without modules. The rewritten angular ngrx project lost 20-30% of the code

But why? There is zero changes with standalone in Angular 17. app.module.ts is not needed in 16 version also.

Glad it was helpful!

Here are videos about my setup. Config files are in the descriptio. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-j6uqOvTRq6I.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-YrLiugDhCuk.html ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-Xa4aOOB7XZo.html

I just do /shared/components/button /shared/components/input

Just import a module in standalone component

Unfortunately you are totally right There are no “global imports”: you need to import a component/pipe/directive every time you use it. ngIf, ngFor, and friends are available in every standalone component generated by the CLI, as the skeleton includes the import of CommonModule. But routerLink for example is not: you need to import RouterModule if you need it. Other frameworks, like Vue for example, allow registering some components globally, to avoid importing them over and over. That’s not the case in Angular.

@@MonsterlessonsAcademy oh I see thank you. I will try using this paradigm, but I think for now it is best to continue using ngModules for practicity in the imports :( at least this gave me a better understanding of how ngModules work 💯

@@MonsterlessonsAcademy So, what is the benefit of using standalone components instead of module?

Just inject it in providers array