Standalone component declaration in Angular - Step-by-Step Execution

Concept Flow - Standalone component declaration

Write @Component decorator with standalone: true

↓

Define component metadata: selector, template, styles

↓

Create component class

↓

Use component directly without NgModule

↓

Angular renders component in DOM

This flow shows how to declare an Angular component as standalone and use it without needing an NgModule.

Execution Sample

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-hello',
  standalone: true,
  template: `<h1>Hello Standalone!</h1>`
})
export class HelloComponent {}

Defines a standalone Angular component with a simple template.

Execution Table

Step	Action	Evaluation	Result
1	Read @Component decorator	Detect standalone: true	Component marked standalone
2	Parse selector 'app-hello'	Store selector	Selector ready for use
3	Parse template `<h1>Hello Standalone!</h1>`	Store template	Template ready to render
4	Create HelloComponent class	Class created	Component logic ready
5	Use <app-hello> in HTML	Angular recognizes standalone component	Component rendered in DOM
6	No NgModule needed	Standalone flag bypasses NgModule	Simpler component usage

💡 Component is standalone, so Angular renders it directly without NgModule.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	Final
standalone	undefined	true	true	true	true
selector	undefined	'app-hello'	'app-hello'	'app-hello'	'app-hello'
template	undefined	undefined	`<h1>Hello Standalone!</h1>`	`<h1>Hello Standalone!</h1>`	`<h1>Hello Standalone!</h1>`
componentClass	undefined	undefined	undefined	HelloComponent class	HelloComponent class

Key Moments - 2 Insights

Why do we not need to declare this component in an NgModule?

Because the component has standalone: true (see execution_table step 1), Angular treats it as independent and does not require NgModule registration.

How does Angular know where to render the component?

Angular uses the selector 'app-hello' (execution_table step 2) to find matching HTML tags and render the component template there.

Visual Quiz - 3 Questions

Look at the execution table, what is the value of 'standalone' after step 1?

A undefined

B false

C true

D null

💡 Hint

Check the 'standalone' variable in variable_tracker after Step 1.

At which step does Angular parse the component's template?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Action' and 'Evaluation' columns in execution_table for template parsing.

If we remove 'standalone: true', what changes in the execution flow?

A Angular requires NgModule to declare the component

B Component still renders without NgModule

C Selector is ignored

D Template is not parsed

💡 Hint

Refer to key_moments about standalone flag and NgModule requirement.

Concept Snapshot

Standalone Component Declaration in Angular:
- Use @Component decorator with standalone: true
- Define selector, template, and styles inside
- Export component class normally
- Use component directly in HTML without NgModule
- Simplifies component usage and modularity

Full Transcript

This lesson shows how to declare an Angular component as standalone by adding standalone: true in the @Component decorator. The selector and template are defined as usual. Angular then treats this component as independent, so it can be used directly in HTML without declaring it in an NgModule. The execution steps include reading the decorator, parsing selector and template, creating the component class, and rendering it in the DOM. Variables like standalone flag, selector, and template are tracked through these steps. Key points include understanding why NgModule is not needed and how Angular uses the selector to render the component. The visual quiz tests understanding of these steps and the effect of removing the standalone flag.