Browse Articles

Understanding Angular Components

 Print   7 min read  
22 Jul 2022

Hello Readers, today you will learn about Angular components. I have added many images, to make it easy to understand for my readers, which makes this article appear a little longer. However, what’s the meaning of diving, if the water is shallow. Right!? So get set and here we go!!


Angular components are building blocks, which in turn form an Application. In a simple language, think of our ecosystem as an Application. Then, water, temperature, oxygen, carbon dioxide, and many more biotic and abiotic factors make the whole ecosystem work as an application. Now, the same concept applies to our Angular application as well. Our app has many components such as header, footer, sidebar which in turn results in an app.

Typically, it is a type of directive with templates, styles, and logic for user interaction. It is exported as a custom HTML tag like as: <my-component></my-component>. The angular component is initialized by an angular dependency injection engine.

Angular Components Page View

A webpage containing an article with comments, categories, a news feed, and header, the footer can be managed using the angular components as given below:

Angular Component Advantages

Now, you all must be thinking, why should we use components? Component inculcates many benefits to that of Angular itself. It provides:

  1. Reusability

    If the same functionality should be exposed in multiple places then, we can reuse it in all these places.

    Say, for example, we have two components: Header and footer. Which should be included on the About Page and Contact Page. Then we simply need to add one tag (which we will cover later in this article) and, your work is done!! You don’t require to add header and sidebar code at each place.

    While working with single-page applications, one should bring the concept of re-usability of the components, util functions templates, and other business logic files because it saves a lot of re-development time and results in better manageable code.

  2. Testability

    It is quite easy to unit test an individual component than a whole unstructured application.

  3. Consistency

    If you know how to structure and write code for one component then, consistency will be there in every component.

  4. High cohesion:

    Components will have functionality only related to themselves.

Difference between Component and Directives

Now, the folks familiar with Angular 1. x might be in dilemma that what is the actual difference between Component and Directives Right!? The major difference between both of them is Directives add behavior to existing DOM element while Components creates their view with attached behavior.,

Creating A Component

Next, the question that arises in our mind is how Angular identifies the components among many other files? The answer is that, if you open any ts file of the component, you will see @component metadata and below it, there will be one class. The @component decorator is responsible for identifying the class as a component and for specifying its metadata.

Now, let us move towards creating our first component. Initially, your app structure will look something like this:

Now, the first inbuilt component that you see in the app. Now, looking at this, you can assume the basic structure of a component. It consists of 4 files: HTML, CSS, TS, SPEC.TS.

Our APP.COMPONENT.HTML the file looks like this:

This file has been created by Angular. It is the basic HTML file. If you run this app, the first page you’ll see as an output will have this HTML written there.


As I have mentioned earlier, you can call component this at any other component by the selector.

TemplateURL depicts the corresponding HTML file for this TS file and the last is styleUrls which represents the styles used by this ts file. Note that this is an array. You can always mention more than one CSS file for one TS file.

Let me just highlight one phenomenon, if you want to use any component call it by its selector name. Let's for example, I want to use the demo component at the demo1 component, then I simply need to call demo’s selector <app-demo></app-demo> (say for example). This will render the demo's HTML at demo1's HTML.

Now, let us create our first component by firing the given below command:

ng g c component_name)

(g stands for generating and c stands for Component)

You can open this terminal using VS Code from (view -> Integrated terminal). As we have previously discussed, a component has 4 files inside it. One new message you'll see is regarding app.module.ts. It is the heart of our app. It contains the global declaration for our all components. After creating a component, our app.module.ts will look like as:

Our component should be imported and added to the declaration array.

Nested Component

Now, if you want to see the task component’s HTML as your output. What would you do!? Remember that Selector concept? Yes, you have to add the task’s selector at APP.COMPONENT.HTML. (Because it is the first component that is being loaded by angular if you want to check how? Check your index.html, there you will find <app-root></app-root> which is selector for the app component).

And here is your output in the browser which shows the content written into the child component but nested from the parent component 

And with this, we have learned a new concept called Nested Component. In the Nested component, we call one component inside another component. The component in which we have called another component is known as the Parent component and called component is known as Child or Nested component.


Angular is a full-fledged framework and the core of the framework is a component, hence using and implementing a component is a common step toward building single-page applications (SPA) where the set of components re-presents an application.

So, components are the essential part of an Angular application. In every application, you will use it, even if you are building a normal app. In short, components are blocks that together make an Angular application.

Hope you have enjoyed reading this article. Keep going and coding!!

Read More: Best Angular Interview Question and Answer

Learn to Crack Your Technical Interview

Accept cookies & close this