/ angular

Dynamically create an Angular component and add it to the DOM - with Angular CDK

Previously I wrote about how to dynamically instantiate a component and add to the DOM. I showed a relatively simple ComponentFactoryService that does exactly that. Today I wanted to show you another way to accomplish the same task. This time with the help of Angular CDK that was recently released by the Angular Material team.

The part of the CDK that is relevant to our case is Portals, and it is specifically designed to deal with the dynamic component creation. In a nutshell, there are two main concepts:

  • Portal: A piece of UI (component or a template) that needs to be created and placed somewhere in an Angular application.

  • PortalHost: A place where the dynamic content can be injected. For example, there is a specific implementation called DomPortalHost that allows you to specify any DOM element (even outside of Angular) as a host, for example document.body.

Without further ado, here is the updated ComponentFactoryService that uses ComponentPortal and DomPortalHost from the CDK:

import {
  ApplicationRef, Componenimport {
  ApplicationRef, ComponentFactoryResolver, ComponentRef,
  Injectable, Injector, Type, ViewContainerRef
} from '@angular/core';

import {
} from '@angular/cdk/portal';

export class ComponentFactoryService {
      private cfr: ComponentFactoryResolver,
      private defaultInjector: Injector,
      private appRef: ApplicationRef) {

   * Instantiates a component and adds it to the DOM.
   * @constructor
   * @param {Type<T>} componentType - Type of the component to create, e.g. "DynamicComponent".
   * @param {HTMLElement | ViewContainerRef} location - (Optional) Location where to inject the
   * component in the DOM, can be an arbitrary HTML element or a ViewContainerRef.
   * @param {Injector} injector - (Optional) Injector that should be used as a parent injector
   * for the component. This is useful only if you want to inject into the component services
   * that are provided in a different place from where ComponentFactoryService is provided.
      componentType: Type<T>,
      location?: HTMLElement | ViewContainerRef,
      injector?: Injector): ComponentRef<T> {

    // The location where the component should live in Angular's logical component tree, where
    // it will be part of change detection, etc.
    // This is different from where the component renders, which is determined by the PortalHost.
    let logicalLocation: ViewContainerRef | undefined = undefined;

    // Host element for rendering the component. By default, use "body".
    let domLocation: HTMLElement = document.body;

    if (location) {
      if (location instanceof HTMLElement) {
        // The location was provided as an arbitrary element and we don't
        // know if it is part of the Angular app, so leave it "undefined"
        // and let the PortalHost take care of attaching it to the Angular app.
        logicalLocation = undefined;
        domLocation = location;
      else {
        // Location is ViewContainerRef, so use it as the logical tree location as well as actuall
        // render location.
        logicalLocation = location;
        domLocation = location.element.nativeElement;

    // Create a Portal based on the given component type
    let componentPortal = new ComponentPortal(componentType, logicalLocation, injector);

    // Create a PortalHost with the specified location as its anchor element
    let bodyPortalHost = new DomPortalHost(
      injector || this.defaultInjector);

    // Attach the Portal to the PortalHost. This will instantiate the component and add
    // it to the DOM. We get a ComponentRef back that we can use to access the component
    // instance as well as destroy the component after we're done with it.
    let componentRef = bodyPortalHost.attach(componentPortal) as ComponentRef<T>;

    return componentRef;
Pavlo Glazkov

Pavlo Glazkov

Programmer. Full stack, with a focus on UI. JavaScript/TypeScript, Angular, Node.js, .NET

Read More