Lazy Load components in Angular using Locality

At the time of its creation, Angular apps load all modules immediately irrespective of their utility and usage in the app. Enter lazy loading. To reduce the number of components the app needs to load and save on resources such as processor power and network bandwidth, we implement the lazy loading pattern in the app. Lazy loading helps keep initial bundle sizes smaller, which in turn helps decrease load times.

Lazy loading of single components has not been possible so far. However, with Angular Ivy (or just Ivy), more abilities are now possible.

Locality in Ivy

Modules are the main building blocks of Angular. These contain several components, directives, pipes, and services. In layman’s terms, today’s application cannot exist without these modules.

Ivy introduces the concept of ‘Locality’ in which a component can exist without a module. With Locality, all the metadata is local to that particular component.
A real-world application of Lazy Loading of Component

Create a new application using Angular CLI. Our app.component.ts file will look like this:

import { Component } from '@angular/core';
	selector: 'app-component',
	templateUrl: './app.component.html',
	styleUrls: ['./app.component.scss']
export class AppComponent {
	title = 'my-app';
ng g greet  — flat — skip-import

In the above command, skip-import will not import the component in the current module. We will load this component inside the module using lazy load.

import { Component, OnInit } from '@angular/core';
  selector: 'greet',
  templateUrl: './greet.component.html',
  styleUrls: ['./greet.component.scss']
export class GreetComponent implements OnInit {
  constructor() { }
  ngOnInit() {

We see that the greet component is created and we will pass data to this component,

@Input() message: string;
@Output() sendEventEmmiter = new EventEmitter()

For now, this is sufficient for the greet component. We will now lazy load the greet component in the app.component. To do this, we have to inject

viewContainerRef and ComponentFactoryResolver
constructor(private vcrf: ViewContainerRef, private cfr: ComponentFactoryResolver) { }

What is viewContainerRef? – This is a container in which one or more views can be attached

What is ComponentFactoryResolver? – This is a simple registry that maps Components to generated ComponentFactory classes.

These classes can be used to create instances of components. Use these to obtain the factory for a given component type, then use the factory’s create() method to create a component of that type.

Create the method

Now create the method to lazy load the component in app.component

loadComponent() {
  import('./greet/greet.component').then(({ GreetComponent }) => {
    let greetComp = this.vcrf.createComponent(

Here we are using promises of JavaScript. These allow us to load the component only if the promise returns successfully. We are also using viewContaierRef, and it’s method createComponent() in which we are passing componentFactoryResolver. These should be able to create the component and host inside that particular viewContainerRef.

If you see, we still are not passing any value to the greetComponent. In the above code, you will notice that we have a variable called greetComp. This variable contains a reference to a lazy loaded component that we can use to pass data.

greetComp.instance.message = 'I am from app.component';
greetComp.instance.sendEventEmmiter.subscribe(data => {

When we combine all the above code so then our loadComponent() method will look like this,

loadComponent() {
  import('./greet/greet.component').then(({ GreetComponent }) => {
    let greetComp = this.greetViewchildRef.createComponent(
    greetComp.instance.message = 'I am from app.component';
    greetComp.instance.sendEventEmmiter.subscribe(data => {

Displaying the result

To display the result, we have to load the greetComponent in the app.component.html file.

  <ng-template #greetComp>
<button (click)="loadComponent()">Load component</button>

Here we use the ng-template to load the greetComponent. We also need to add viewChild() to show the component data.

@ViewChild('greetComp', {read: ViewContainerRef})
private greetViewchildRef: ViewContainerRef

Note that if we want to use any module, then we need to add the decorator to the component itself, and then import the module within it.

  declarations: [GreetComponent],
  imports: [FormsModule]
class GreetComponentModule {}


We can create the component using a normal flow. However, what if we want to use the created component only for a specific action? If we use the usual way, we can reduce our application load by using a lazy load component.

To view the full application click here: you liked this post, here are a few more that may interest you:

Leave a Comment

Your email address will not be published. Required fields are marked *

About the author

Sushil Joshi

Sushil is a UI and UX developer at Synerzip. He has been developing interfaces for more than five years and has extensive knowledge of Bootstrap Framework, CSS3, and SCSS (CSS preprocessor). Sushil holds a Masters in Computer Applications from Pune University.

Talk to us

Scale your engineering team, decrease time to market and save at least 50 percent with our optimized Agile development teams.

Contact us