AMP 21: Angular's Future with Standalone Components by Manfred Steyer

Angular Master Podcast

Innehåll tillhandahållet av Dariusz Kalbarczyk. Allt poddinnehåll inklusive avsnitt, grafik och podcastbeskrivningar laddas upp och tillhandahålls direkt av Dariusz Kalbarczyk eller deras podcastplattformspartner. Om du tror att någon använder ditt upphovsrättsskyddade verk utan din tillåtelse kan du följa processen som beskrivs här https://sv.player.fm/legal.

2y ago 15:21

M4A•Episod hem

What's up everyone, this is Dariusz Kalbarczyk co-founder of NG Poland, JS Poland, AngularMaster.dev & WorkshopFest.dev. Welcome back to the Angular Master Podcast.

Today, together with Manfred Steyer, who is an excellent Speaker, Trainer, Consultant and Author with focus on Angular. We will talk about Standalone Components

Link to book a place on the webinar:

https://angularmaster.dev/webinars/

Originally, the idea was to not implement NgModules for Angular 2, as it was called back then. Why have they even been introduced in the first place?
Why does the Angular team want to make them optional?
How will working without NgModules look like?
Isn't importing the whole context into Standalone Components exhausting?
What's with existing source code and libs? Are Standalone Components compatible?
Currently, the Angular Router uses NgModules, e. g. for lazy loading. How will this work in the future?
What's with forRoot and forChild methods?
Without NgModules, how can we structure our Angular applications in the future?

--- Send in a voice message: https://podcasters.spotify.com/pod/show/angular-master/message

60 episoder

#Tech #Dariusz Kalbarczyk