Migrating from NgModules in Angular - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main reason Angular is moving away from NgModules?

Angular moves away from NgModules to simplify app structure, improve build speed, and enable standalone components that reduce boilerplate.

beginner

How do standalone components differ from components declared in NgModules?

Standalone components declare their own dependencies and don't need to be listed in NgModules, making them more independent and easier to reuse.

intermediate

What decorator replaces NgModule metadata when using standalone components?

The @Component decorator with the 'standalone: true' property replaces NgModule metadata for standalone components.

intermediate

How can you import other components or directives into a standalone component?

Use the 'imports' array inside the @Component decorator to include other standalone components, directives, or pipes.

intermediate

What is a key benefit of migrating to standalone components regarding lazy loading?

Standalone components simplify lazy loading by allowing direct import of components without needing separate NgModules.

What property do you add to a component to make it standalone?

A standalone: true

B module: true

C independent: true

D isolated: true

The 'standalone: true' property in the @Component decorator marks a component as standalone.

Which Angular feature becomes unnecessary when using standalone components?

A Pipes

B Services

C Directives

D NgModules

Standalone components reduce or remove the need for NgModules by managing their own dependencies.

Where do you specify other components or directives a standalone component uses?

A In the main.ts file

B In the NgModule's declarations

C In the 'imports' array of the @Component decorator

D In the package.json

Standalone components list dependencies in the 'imports' array inside their @Component decorator.

What is a benefit of standalone components for app startup time?

A No change in startup time

B Faster startup due to less boilerplate and simpler dependency graph

C Slower startup due to more files

D Requires manual optimization

Standalone components reduce boilerplate and simplify dependencies, improving startup speed.

How do you bootstrap an Angular app without NgModules?

A Pass the standalone root component directly to bootstrapApplication()

B Use platformBrowserDynamic().bootstrapModule()

C Use a main NgModule

D Bootstrap is not needed

With standalone components, you bootstrap the app by passing the root standalone component to bootstrapApplication().

Explain how to migrate an Angular component from NgModule-based to standalone.

Focus on decorator changes and dependency management.

Describe the benefits of using standalone components over NgModules in Angular.

Think about developer experience and app performance.

Practice

1. What is the main benefit of migrating from NgModules to standalone components in Angular?

easy

A. Simplifies the app by removing the need for NgModules

B. Requires more boilerplate code for each component

C. Makes the app slower to load

D. Forces use of class-based components only

Solution

1. Step 1: Understand NgModules role

   NgModules group components and services but add complexity.

2. Step 2: Benefits of standalone components

   Standalone components remove NgModules, making the app simpler and easier to maintain.

3. Final Answer:

   Simplifies the app by removing the need for NgModules -> Option A

4. Quick Check:

   Standalone components simplify Angular apps by removing NgModules [OK]

Hint: Standalone means no NgModules needed, simpler setup [OK]

Common Mistakes:

• Thinking standalone components require more code
• Believing NgModules improve app speed
• Confusing standalone with class-based restriction

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

easy

A. @Component({ standalone: false, selector: 'app-hello', template: 'Hello' })

B. @Component({ module: true, selector: 'app-hello', template: 'Hello' })

C. @NgModule({ standalone: true, declarations: [HelloComponent] })

D. @Component({ standalone: true, selector: 'app-hello', template: 'Hello' })

Solution

1. Step 1: Identify standalone component syntax

   The correct property is standalone: true inside the @Component decorator.

2. Step 2: Check other options

   The other options are incorrect: one sets standalone: false, another uses invalid module property, and one misuses @NgModule.

3. Final Answer:

   @Component({ standalone: true, selector: 'app-hello', template: '<p>Hello</p>' }) -> Option D

4. Quick Check:

   standalone: true inside @Component decorator [OK]

Hint: Look for standalone: true inside @Component decorator [OK]

Common Mistakes:

• Using @NgModule instead of @Component for standalone
• Setting standalone to false or missing it
• Confusing module property with standalone

3. Given this code snippet, what will be the output when the app runs?

import { bootstrapApplication } from '@angular/platform-browser';
import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  standalone: true,
  template: `
{{ title }}
`
})
export class AppComponent {
  title = 'Hello Angular Standalone';
}

bootstrapApplication(AppComponent);

medium

A. undefined

B. Error: bootstrapModule is required

C. Hello Angular Standalone

D. Blank page with no content

Solution

1. Step 1: Understand bootstrapApplication usage

   Using bootstrapApplication with a standalone component boots the app correctly.

2. Step 2: Check component template and data

   The template shows <h1>{{ title }}</h1> and title is set to 'Hello Angular Standalone'.

3. Final Answer:

   <h1>Hello Angular Standalone</h1> -> Option C

4. Quick Check:

   bootstrapApplication with standalone component renders {{ title }} [OK]

Hint: bootstrapApplication runs standalone component, shows title [OK]

Common Mistakes:

• Expecting bootstrapModule instead of bootstrapApplication
• Assuming title is undefined without constructor
• Thinking template won't render without NgModule

4. Identify the error in this code snippet migrating from NgModules:

import { bootstrapApplication } from '@angular/platform-browser';
import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  standalone: true,
  template: `
Welcome
`
})
export class AppComponent {}

bootstrapApplication(AppComponent, {
  providers: []
});

medium

A. bootstrapApplication requires bootstrapModule instead

B. Missing imports array for dependencies in @Component

C. Standalone components cannot have providers

D. Selector 'app-root' is invalid for standalone components

Solution

1. Step 1: Check standalone component dependencies

   If the component uses other modules or components, they must be listed in the imports array inside @Component.

2. Step 2: Analyze given code

   The component has no imports array. The template uses *ngIf, which requires CommonModule in imports.

3. Final Answer:

   Missing imports array for dependencies in @Component -> Option B

4. Quick Check:

   Standalone components need imports: [CommonModule] for directives like *ngIf [OK]

Hint: Standalone components need imports for dependencies [OK]

Common Mistakes:

• Thinking bootstrapApplication needs bootstrapModule
• Believing providers are disallowed in standalone
• Assuming selector rules changed for standalone

5. You want to migrate an Angular app from NgModules to standalone components. Which combination correctly replaces the traditional bootstrap method and module imports?

1. Use bootstrapApplication() instead of platformBrowserDynamic().bootstrapModule()
2. Add standalone: true to components
3. Use imports array inside @Component for dependencies
4. Keep NgModule declarations as before

hard

A. Apply steps 1, 2, and 3; remove NgModules completely

B. Only step 1 is needed; keep NgModules and declarations

C. Apply steps 2 and 4; bootstrapModule remains required

D. Use step 4 only; standalone components are optional

Solution

1. Step 1: Replace bootstrap method

   Use bootstrapApplication() to start the app without NgModules.

2. Step 2: Convert components to standalone

   Add standalone: true to components to remove NgModule dependency.

3. Step 3: Manage dependencies with imports

   Use imports array inside @Component to include needed modules or components.

4. Step 4: Remove NgModules

   NgModules are no longer needed and should be removed for full migration.

5. Final Answer:

   Apply steps 1, 2, and 3; remove NgModules completely -> Option A

6. Quick Check:

   bootstrapApplication + standalone: true + imports array, no NgModules [OK]

Hint: Use bootstrapApplication + standalone + imports, drop NgModules [OK]

Common Mistakes:

• Trying to keep NgModules with bootstrapApplication
• Forgetting to add standalone: true to components
• Not using imports array for dependencies