Standalone component declaration in Angular

Introduction

Standalone components let you create Angular components without needing a module. This makes your code simpler and easier to manage.

When you want to build a small, reusable UI piece quickly.

When you want to avoid creating extra Angular modules for simple components.

When you want to improve app startup time by reducing module overhead.

When you want to use Angular's new recommended way to build components.

When you want to share components easily across different parts of your app.

Syntax

Angular

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

@Component({
  selector: 'app-example',
  standalone: true,
  template: `<p>Hello from standalone component!</p>`,
  imports: [] // optional: other standalone components or directives
})
export class ExampleComponent {}

The key part is standalone: true inside the @Component decorator.

You can add other standalone components or directives in the imports array if needed.

Examples

A basic standalone component with a simple template.

Angular

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

@Component({
  selector: 'app-simple',
  standalone: true,
  template: `<h1>Simple Standalone</h1>`
})
export class SimpleComponent {}

This standalone component imports CommonModule to use Angular features like event binding.

Angular

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

@Component({
  selector: 'app-with-common',
  standalone: true,
  imports: [CommonModule],
  template: `<button (click)="count = count + 1">Clicked {{count}} times</button>`
})
export class WithCommonComponent {
  count = 0;
}

Sample Program

This standalone component shows a counter. It uses Angular signals to track the count and updates the display when the button is clicked.

Angular

import { Component, signal } from '@angular/core';
import { CommonModule } from '@angular/common';

@Component({
  selector: 'app-counter',
  standalone: true,
  imports: [CommonModule],
  template: `
    <h2>Counter</h2>
    <button (click)="increment()">Increment</button>
    <p>Count: {{ count() }}</p>
  `
})
export class CounterComponent {
  count = signal(0);

  increment() {
    this.count.set(this.count() + 1);
  }
}

Important Notes

Standalone components do not need to be declared in any NgModule.

You can use imports to bring in other standalone components or Angular modules.

Standalone components help reduce boilerplate and improve app modularity.

Summary

Standalone components simplify Angular by removing the need for NgModules.

Use standalone: true in the component decorator to declare them.

They can import other standalone components or modules via the imports array.

Practice

1. What does adding standalone: true in an Angular component's decorator do?

easy

A. Disables change detection for the component.

B. Makes the component lazy-loaded automatically.

C. Registers the component globally in the Angular app.

D. Declares the component as standalone, removing the need for NgModule declaration.

Solution

1. Step 1: Understand Angular component declaration

   Normally, Angular components must be declared inside an NgModule to be usable.

2. Step 2: Effect of standalone: true

   Setting standalone: true allows the component to be used without declaring it in any NgModule.

3. Final Answer:

   Declares the component as standalone, removing the need for NgModule declaration. -> Option D

4. Quick Check:

   Standalone component = no NgModule needed [OK]

Hint: Standalone means no NgModule needed for the component [OK]

Common Mistakes:

• Thinking standalone makes component lazy-loaded
• Assuming standalone registers component globally
• Confusing standalone with change detection settings

2. Which of the following is the correct syntax to declare a standalone component in Angular?

easy

A. @Component({ selector: 'app-test', standalone: true, template: 'Test' }) export class TestComponent {}

B. @Component({ selector: 'app-test', standalone: false, template: 'Test' }) export class TestComponent {}

C. @Component({ selector: 'app-test', standalone: true, templateUrl: 'test.html' }) export class TestComponent {} NgModule({ declarations: [TestComponent] })

D. @Component({ selector: 'app-test', standalone: true }) export class TestComponent { template: 'Test' }

Solution

1. Step 1: Check the standalone property usage

   The standalone property must be set to true inside the @Component decorator.

2. Step 2: Verify template declaration and class export

   The template can be inline with template or external with templateUrl. The class must be exported properly.

3. Final Answer:

   @Component({ selector: 'app-test', standalone: true, template: '<p>Test</p>' }) export class TestComponent {} -> Option A

4. Quick Check:

   Standalone true inside @Component with inline template [OK]

Hint: Standalone true must be inside @Component decorator [OK]

Common Mistakes:

• Setting standalone to false
• Declaring template outside the decorator
• Mixing NgModule declaration with standalone component

3. Given this standalone component declaration, what will be the rendered output?

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

@Component({
  selector: 'app-hello',
  standalone: true,
  template: `
Hello, {{ name }}!
`
})
export class HelloComponent {
  name = 'Angular';
}

medium

A. No output because component is standalone

B. Hello, {{ name }}!

C. Hello, Angular!

D. Error: Property 'name' is undefined

Solution

1. Step 1: Understand template interpolation

   The template uses {{ name }} which Angular replaces with the component's property value.

2. Step 2: Check the property value

   The component defines name = 'Angular', so interpolation outputs 'Angular'.

3. Final Answer:

   <h1>Hello, Angular!</h1> -> Option C

4. Quick Check:

   Template interpolation replaces {{ name }} with 'Angular' [OK]

Hint: Interpolation shows property value inside template [OK]

Common Mistakes:

• Thinking interpolation shows raw {{ name }}
• Assuming standalone disables property binding
• Expecting runtime error for missing property

4. Identify the error in this standalone component declaration:

@Component({
  selector: 'app-sample',
  standalone: true,
  template: '
Sample
',
  imports: [CommonModule]
})
export class SampleComponent {}

medium

A. The imports array must be inside @NgModule, not @Component

B. Missing import statement for CommonModule

C. CommonModule must be imported from '@angular/common' and declared in imports

D. CommonModule cannot be imported in standalone components

Solution

1. Step 1: Check imports usage in standalone component

   Standalone components can import modules like CommonModule via the imports array in the decorator.

2. Step 2: Verify import statement presence

   The code uses CommonModule in imports but does not import it from '@angular/common' at the top.

3. Final Answer:

   Missing import statement for CommonModule -> Option B

4. Quick Check:

   Imports array needs proper import statements [OK]

Hint: Always import modules before using in imports array [OK]

Common Mistakes:

• Thinking imports array is invalid in @Component
• Forgetting to import CommonModule from '@angular/common'
• Assuming CommonModule cannot be used in standalone components

5. You want to create a standalone Angular component that uses another standalone component called ButtonComponent. How should you declare the imports array in your component decorator?

hard

A. @Component({ standalone: true, imports: [ButtonComponent], template: '' })

B. @Component({ standalone: true, imports: ['ButtonComponent'], template: '' })

C. @Component({ standalone: true, imports: [NgModule], template: '' })

D. @Component({ standalone: true, template: '' })

Solution

1. Step 1: Understand how to use other standalone components

   Standalone components can import other standalone components by listing them in the imports array.

2. Step 2: Correct syntax for imports array

   The imports array must contain the component class itself, not a string or NgModule.

3. Final Answer:

   @Component({ standalone: true, imports: [ButtonComponent], template: '<app-button></app-button>' }) -> Option A

4. Quick Check:

   Imports array includes component classes, not strings [OK]

Hint: Import component classes directly, not strings or modules [OK]

Common Mistakes:

• Using string names instead of component classes in imports
• Importing NgModule instead of component
• Omitting imports array when using other standalone components