Introduction to Angular modules: Part 1
Angular apps are modular and Angular has its own modularity system called NgModules.
Modular programming is a software design technique that emphasizes separating the functionality of a program into independent, interchangeable modules, such that each contains everything necessary to execute only one aspect of the desired functionality.
NgModules are containers for a cohesive block of code dedicated to an application domain, a workflow, or a closely related set of capabilities.
They can contain components, service providers, and other code files whose scope is defined by the containing NgModule.
They can import functionality that is exported from other NgModules, and export selected functionality for use by other NgModules.
Every Angular app has at least one NgModule class, the root module.
The root module is conventionally named AppModule and resides in a file named app.module.ts.
You launch your app by bootstrapping the root NgModule.
While a small application might have only one NgModule, most apps have many more feature modules.
The root NgModule can include child NgModules in a hierarchy of any depth.
NgModule metadata
An NgModule is defined by a class decorated with @NgModule().
The @NgModule() decorator is a function that takes a single metadata object, whose properties describe the module.
The most important properties are:
declarations: The components, directives, and pipes that belong to this NgModule.
exports: The subset of declarations that should be visible and usable in the component templates of other NgModules.
imports: Other modules whose exported classes are needed by component templates declared in this NgModule.
providers: Creators of services that this NgModule contributes to the global collection of services; they become accessible in all parts of the app. You can also specify providers at the component level, which is often preferred.
bootstrap: The main application view, called the root component, which hosts all other app views. Only the root NgModule should set the bootstrap property.
Here's a simple root NgModule definition.
// src/app/app.module.ts
import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
@NgModule({
imports: [ BrowserModule ],
providers: [ Logger ],
declarations: [ AppComponent ],
exports: [ AppComponent ],
bootstrap: [ AppComponent ]
})
export class AppModule { }
Note: AppComponent is included in the exports list here for illustration; it isn't actually necessary in this example. A root NgModule has no reason to export anything because other modules don't need to import the root NgModule.
Next
Introduction To Angular Modules Part 2: NgModules And Components
Introduction To Angular Modules Part 3: NgModules Vs JavaScript Modules And Angular Libraries
Credit: Angular.io
data meta Modules NgModule
