Video details

Angular Ivy: How are entry components handled? | Yvonne Allen


Yvonne Allen

With Angular Ivy, entry components are no more. Join me as we reminisce about our time with entry components and learn how these type of components are being handled today in Angular 9.


Hello, everyone, my name is Yvonne Allen, and I'm Yvonne with the phone. Angie, come in. My news is real. Once again, everyone OK? OK, thank you, Captain Babyface. OK, everybody, we have breaking news. We have good news and bad news. The bad news is our dear friend Inchy component's is out of here. For those of you who don't know, your components first appeared back on the scene of the ANGULAR in the version to where his main job was to help us fill Angular with components. We needed it and inserted into our angular application at runtime. And taking. Captain Babyface, what is the good news, Africa? Oh, the news is bad news. OK. OK, guys, we have good news and components is. Out of here, if you were one of the ones who had to do with pop ups in your English application, but instead ended up following your own defeat as you came up with this error here. I'm pretty sure you can appreciate now, but Angola has to offer with the new angle with not having to deal with Angola components, so. Angular, the anger the core team has, your these guys, they heard your cries, they heard your tweets, the Haridwar blogs and your GitHub issues, and they decided to give the opponents the boot. What exactly did happen that changed and major components obsolete? Well, we here at Indico News decided to go and get the inside scoop and go directly to the angular core team to find out exactly what happens. So let's go behind the scenes and get a behind the scenes look. OK, so prior to angular nine angular generated energy factories for all components declared in a template. In fact, these were exact were actually what was used behind the scenes doing runtime instead of angular components, which if we didn't know about it, was what caused a lot of the confusion. So this was done in conjunction with components, the component factor resolver to enable things like tree shaking. Now, because of these factors, ANGULAR could no longer will could not use dynamic components at runtime because they didn't have any energy factories. Therefore, the entry components array was used to form ANGULAR about these these dynamic opponents so that their factis would be available to Engler at runtime so that you can now use things like cockups. Now, now, as of ANGULAR nine, there are no more energy factories. Out of here, all of the information needed to the components are attached to static properties, in fact, respectively, so that angler will know exactly how to run these components and you don't need into components anymore. So in the words of our dear friend Alex from the England team who actually worked on the compiler, the reference to a component now is indeed a reference to this factory. So to wrap this all up in the brain, get around it, your components are out, angular ivy is awesome, components are smarter than you, Jesus, and or whoever you are. And if you haven't done so already, upgrade your Anglo application to Angular Non so you can join in the fun with us. And now I would like to give a special thanks to adits from the legal team for helping me out in Rob as well, for helping me out and giving me the inside scoop that we would not have had had it not been for them and for income or allow me to present today. It's a great day for bringing this awesome, awesome, awesome virtual conference to us in spite of everything that's happening out in the world. So stay stay safe, guys. Keep the social distance and have fun.