Introduction to Angular Modules or ngModule

The building blocks of Angular Applications consist of Components, Templates, Directives, Pipes, and Services. We build a lot of such blocks to create a complete application. As the application grows bigger in size managing these blocks become difficult. The Angular Provides a nice way to organize these blocks in a simple and effectively using Angular modules (Also known as ngModule).

The Module is an overloaded term. It means different things depending on the context. There are two kinds of modules that exist in Angular itself. One is the JavaScript Module and the other one is Angular Module.

What is Angular Module

The Angular module (also known as ngModule) helps us to organize the application parts into cohesive blocks of functionality. Each block focuses on providing a specific functionality or a feature.

The Angular module must implement a specific feature. The Components, Directives, Services that implement such a feature, will become part of that Module. 

The Modular design helps to keep the Separation of concerns. Keep the features together. Makes it easy to maintain the code. Makes it easier to reuse the code.

The Angular itself is built on the concept of Modules. The @angular/core is the main Angular module, which implements Angular’s core functionality, low-level services, and utilities.

The Features like Forms, HTTP, and Routing are implemented as separate Feature modules such as FormsModuleHttpClientModule, and RouterModule. There are many third-party libraries built around Angular such as Material DesignIonic, etc.

Angular Applications are assembled from the modules. The module exports Component, directive, service, pipe, etc, which can be then imported into another module

JavaScript Modules vs. NgModules

JavaScript Modules

The JavaScript Modules, which also go by the name JS modules or ES modules, or ECMAScript modules are part of the JavaScript Language. The JS Modules are stored in a file. There is exactly one module per file and one file per module. These modules contain small units of independent, reusable code. They export a value, which can be imported and used in some other module.

The following is a Javascript Module that exports the SomeComponent.

The SomeOtherComponent is another JavaScript Module, that imports and uses the SomeComponent.

How to Create an Angular Module

The Angular Module must declare the Components, Pipes, and Directives it manages. We Create the Angular Modules by decorating it with the ngModule decorator.


The NgModule() decorator is a function that takes a single metadata object, whose properties describe the module. The most important properties are as follows.

Declarations array

This is where components, directives, and pipes that belong to this NgModule are declared.

You should add only those, which belong to this module. The Component cannot belong to more than one module.

The services must not be declared here. They are defined in the Angular Providers array.

Providers array

The Services, which you want to add to the global collection of services are added here. The services are then available for injection via dependency injection.

Remember :
Declarations are for Components, Directives & Pipes. 
Providers are for Services

Services are global in scope. Services added to Providers array are available for injection in the entire application

Suggested Readings
Angular Services  
Dependency Injection in Angular
Angular Injector
Providers in Angular
Angular Hierarchical Dependency Injection

Imports array

If you want this ngModule require any feature or functionality, then those modules need to be imported here. Any components, directives, and pipes that are defined and exported in that module can be used in this module.

Exports array

If you want other modules to use the component, pipes, directives of this NgModule, then those must be specified here.

Only those components declared here are visible to the other ngModules, when they import this module.


The main component of this module, which needs to be loaded when the module is loaded is specified here.

This is a must if you are the first module ( called the root module) that is loaded when the Angular App starts. It is the responsibility of the root module to load the first view and it is done by specifying the component here.

If the module is not the root module, then you should keep this blank

Suggested Reading

How Angular Bootstraps your Application


The components that are dynamically loaded needs to be declared here.

The components are loaded when angular

  • Finds the Component Selector in the HTML
  • Declared in the bootstrap array
  • Declared in the root definition

If your component is not listed any of the above, then it needs to be declared in EntryComponent so that Angular knows where to find them and compile them.

The following image should make it clear, how the ngModule metadata works

Angular Module or ngModule

Angular Module Example

Let us create an example application with multiple modules to demonstrate the use of the Angular Modules. 

Create the application

Use npm start to run the program and test everything is ok.

The App Contains two Modules. i.e. AppModuleAppRoutingModule

Routing Module

The AppRoutingModule is an Angular Module, which specifically defines the application Routes

This module does not contain any components, pipes or directives. Hence it does not need to declare anything in the declaration array

No services are part of this Module, Hence providers array is also not needed.

The Angular RouterModule is needed for the routing to work, Hence it is imported. The Routermodule requires the routes to work, hence it is passed to the RouterModule in the forRoot method.

The application needs only one instance of the services provided by the RouterModule.  But every Angular module might contain routes of its own and needs to import RouterModule and register the routes.

Angular has a nice way to solve this problem. The Services are registered only if you call the forRoot method. forRoot method must be called only once and in the Root module. In the other modules, we will be using the forChild method to register the routes

Root Module

The first module that gets loaded is called Root Module, which is conventionally named as AppModule and is automatically created by the Angular CLI.

The following is the auto-generated code of the AppModule. The class is decorated with the @NgModule decorator

The AppModule has only one component i.e AppComponent and it does not have any pipes or directives. Hence the declaration array contains only AppComponent

The imports metadata should contain the other modules that are being used by this module. Hence it imports the BrowserModule, which is an Angular Library. It also requires Routes, hence we are importing AppRoutingModule

The AppModule does not define any services. Hence the providers array is empty

Finally, we need to load the AppComponent when the App starts, hence we define it in bootstrap array

Creating a Module

Let us add another Module to our above application.

Create a folder home under src/app folder


Let us add three components. HomeComponent, AboutUsComponent, ContactUsComponent.

Create a folder called pages under the home folder. Create a three folder under pages aboutus, contactus & home.








Home Module

Now, our components are ready, we can now create the HomeModule

Create the home.module.ts under the home folder

We decorate the HomeModule class with @NgModule to let Angular know that it is an Angular Module

Next, use the declarations array to declare the three components that we have created.

The HomeModule do not expose any services, hence we keep the providers array empty

We are keeping the Routes in the module itself. You can create a separate routing module similar to the AppRoutingModule. That will help to keep the HomeModule code clean.

HomeModule requires CommonModule hence it is added to the imports array. The RouterModule module is imported and routes are registered with the call to forChild(routes). forChild registered the routes but does not register any services.


Using HomeModule in AppModule

The next step is to import the HomeModule in the AppModule. First import the HomeModule

Next, add HomeModule to the imports metadata of the @ngModule

Next, we need to use the Components of the HomeModule. Open the app.component.ts and add the following code

All we have done is to use them routerLink to create a menu item. 

Suggested Readings:
Angular Router

Copy the following CSS to app.component.css

Finally, run the app


In this tutorial, we learned what is Angular Modules are and how to create an Angular Module.

9 thoughts on “Introduction to Angular Modules or ngModule”

  1. Hello! The section at the end when you add the menu is a bit unclear. It states to add HTML to a .TS file but that doesn’t make sense.

Leave a Comment

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

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Scroll to Top