Session

Taming Webcomponents with Angular

With Angular Elements we can easily create custom elements which allows our app to be injected as a webcomponent on any HTML page. This might be helpful if we want to embed a microfrontend widget on a page using a different Javascript framework. But what if we want to place multiple custom elements on the same page? Or if we want more complex routed applications being bundled as a webcomponent? Do webcomponents help us solving the versioning problem, having Angular applications with different versions on the same page? This talk will give you some ideas about the potential and the limits of webcomponents. Because in the end, they might need to share the same browser window.

Cathrin Möller

Professor for applied computer science at Hochschule Fulda

Fulda, Germany

Actions

Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.

Jump to top