You didn’t yet get into Angular Elements? Then it’s time to give it a go! In this article we’re going to see what Angular Elements actually are, why they are useful and how to create our first Angular Element out of a plain component.

Egghead course: Getting Started with Angular Elements

Heads up! I’ve created a 40min course on Egghead.io that introduces you to Angular Elements, step by step.

Here’s the intro video for the course:

The course walks you through..

View the entire course here.

What are Angular Elements?

Angular Elements is the new kid on the block in the Angular ecosystem. Elements allows you to automatically convert (or wrap) every Angular Component as “Custom Element”. Custom Elements are one of the specs under the umbrella term of Web Components. That opens up a loooot of new possibilities for Angular like

dynamically instantiating components - but not with a ComponentFactoryWhatever but in the form of having it in a HTML string sent from the server for instance, a typically use case for CMS systems. It also allows us to instantiate a component using the browser native document.createElement('...') API.

but not with a ComponentFactoryWhatever but in the form of having it in a HTML string sent from the server for instance, a typically use case for CMS systems. It also allows us to instantiate a component using the browser native API. compiling Angular components as custom elements to be consumed “outside” of an Angular app. Assume you build some cool widgets you wanna reuse within your organization. But not everyone uses Angular, or even has a SPA. In such situation you can still compile your Angular component (as Angular Element) into a single JS file and use it wherever you need it

to be consumed “outside” of an Angular app. Assume you build some cool widgets you wanna reuse within your organization. But not everyone uses Angular, or even has a SPA. In such situation you can still compile your Angular component (as Angular Element) into a single JS file and use it wherever you need it upgrading your AngularJS app - there are different strategies available. Angular Elements are a new option to upgrade a legacy AngularJS app simply by embedding Angular Elements for certain pages/components.

Why?

Why we need Angular Elements? There are plenty of reasons and use cases:

Implementing more dynamic Angular Applications (i.e. CMS systems)

Embed Angular Components in non-Angular Apps (i.e. sharing between teams at big organizations)

Enhancing existing HTML pages (not everything is & should be created as single page app)

Upgrading from AngularJS to Angular (i.e. by embedding Angular Elements in AngularJS apps)

Micro Frontends

…

Creating your first Angular Element

Ready? Let’s jump straight in and create our first element.

First of all we need to install the new Angular Elements package (which usually doesn’t come installed by default). Instead of installing and configuring it manually, we can use the Angular CLI’s ng add command:

$ ng add @angular/elements

Next, we create a sample component - we call it GreeterComponent - that will be used as an Angular Element:

import { Component , OnInit } from '@angular/core' ; @Component ({ // selector: 'do-greet', template : ` <div> Hi there! </div> ` , styles : [] }) export class GreeterComponent implements OnInit { constructor () {} ngOnInit() { } }

Note I do comment the selector . The reason is that with Angular Elements, we define the selector at the moment of registring the Angular Element. The selector in the component would be obsolete and only misleading for other developers. Therefore, I’m commenting it, hence communicating to my peers that this component will probably be registered in a different way.

Now that we have our component, we need to register it as a Custom Element by using the @angular/elements package we’ve installed previously. The registration takes place in the corresponding NgModule :

import { NgModule , Injector } from '@angular/core' ; ... import { GreeterComponent } from './greeter.component' ; import { createCustomElement } from '@angular/elements' ; @NgModule ({ ... declarations : [..., GreeterComponent ], entryComponents : [ GreeterComponent ], ... }) export class AppModule { constructor ( injector : Injector ) { const el = createCustomElement ( GreeterComponent , { injector : injector }); customElements . define ( 'do-greet' , el ); } }

Now that the element is registered, we can even dynamically insert it into our component using the native browser DOM API. Something like:

const containerEl = document . getElementById ( 'some-container' ); containerEl . innerHTML = '<do-greet></do-greet>' ;

Note, this wouldn’t work with a plain Angular Component. For dynamically instantiating those we need to do some more work.

I made this Egghead lesson free for you, so you can watch the process by yourself:

Here’s also a running Stackblitz for you.

Browser support and Polyfills?

Well…support is on the way, but we’re not there yet: https://caniuse.com/#feat=custom-elementsv1. Some browsers need polyfills.

If you run your Angular Elements app after installing the @angular/elements package, you might get such an error message:

TypeError: Failed to construct 'HTMLElement': Please use the 'new' operator, this DOM object constructor cannot be called as a function.

There are a couple of things we need to install to get it running in all browsers.

$ npm i @webcomponents/webcomponentsjs

Then open your polyfills.ts and at the very end of the file, add the following lines:

// if you are compiling to ES5 (check tsconfig.json) then you need this import '@webcomponents/webcomponentsjs/custom-elements-es5-adapter.js' ; // for browser not supporting custom elements import '@webcomponents/custom-elements/custom-elements.min.js' ;

Also note, if you’re targeting IE11, make sure to un-comment other imports in the polyfills.ts as well (such as core-js etc.)

Conclusion

That should be it. If you wanna learn more make sure to checkout my course 🙏 or hit me on Twitter.

I’m pretty sure Angular Elements are going to play a major role in the coming years, especially also after the new renderer Ivy lands (as it will come with smaller bundles). And it’s not only about compiling Angular Components to be exported as standalone Custom Elements, but also for just having them dynamically load in your existing Angular app or for CMS based systems, where the server already returns pre-made HTML code, containing component tags which your Angular app needs to boot and interpret.

Questions? Thoughts? Hit me up on Twitter