Root module (AppModule) structure in Angular - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the core Angular module.

Angular

import { [1] } from '@angular/core';

Drag options to blanks, or click blank then click option'

AInjectable

BComponent

CDirective

DNgModule

Attempts:

3 left

💡 Hint

Common Mistakes

Importing Component instead of NgModule

Using Injectable which is for services

Forgetting to import anything

The NgModule decorator is imported from '@angular/core' to define Angular modules.

2fill in blank

medium

Complete the code to declare the root component in the module.

Angular

@NgModule({
  declarations: [[1]],
  imports: [],
  bootstrap: []
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

AAppComponent

BBrowserModule

CHttpClientModule

DFormsModule

Attempts:

3 left

💡 Hint

Common Mistakes

Putting BrowserModule in declarations instead of imports

Forgetting to declare the root component

Confusing declarations with bootstrap

The root component AppComponent must be declared in the declarations array of the root module.

3fill in blank

hard

Fix the error in the bootstrap array to start the app with the root component.

Angular

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule],
  bootstrap: [[1]]
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

AHttpClientModule

BBrowserModule

CAppComponent

DFormsModule

Attempts:

3 left

💡 Hint

Common Mistakes

Putting BrowserModule in bootstrap instead of imports

Leaving bootstrap array empty

Using a service or module in bootstrap

The bootstrap array must contain the root component AppComponent to launch the app.

4fill in blank

hard

Fill both blanks to import BrowserModule and declare AppComponent correctly.

Angular

import { NgModule } from '@angular/core';
import { [1] } from '@angular/platform-browser';
import { [2] } from './app.component';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule],
  bootstrap: [AppComponent]
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

ABrowserModule

BHttpClientModule

CAppComponent

DFormsModule

Attempts:

3 left

💡 Hint

Common Mistakes

Importing HttpClientModule instead of BrowserModule

Importing FormsModule instead of AppComponent

Mixing up import paths

BrowserModule is imported from '@angular/platform-browser' to enable browser features.

AppComponent is imported from the local file './app.component' to declare the root component.

5fill in blank

hard

Fill all three blanks to complete the root module with declarations, imports, and bootstrap arrays.

Angular

@NgModule({
  declarations: [[1]],
  imports: [[2]],
  bootstrap: [[3]]
})
export class AppModule {}

Drag options to blanks, or click blank then click option'

AAppComponent

BBrowserModule

DHttpClientModule

Attempts:

3 left

💡 Hint

Common Mistakes

Using HttpClientModule in imports instead of BrowserModule

Forgetting to bootstrap AppComponent

Mixing declarations and imports

The declarations array must include AppComponent to declare the root component.

The imports array must include BrowserModule to enable browser features.

The bootstrap array must include AppComponent to start the app with the root component.

Practice

1. What is the main purpose of the AppModule in an Angular application?

easy

A. To declare components and import modules needed for the app

B. To style the application globally

C. To handle HTTP requests

D. To manage routing only

Solution

1. Step 1: Understand the role of AppModule

   The AppModule is the root module that organizes the app's components and imports other modules.

2. Step 2: Identify what AppModule does

   It declares components and imports modules needed for the app to work properly.

3. Final Answer:

   To declare components and import modules needed for the app -> Option A

4. Quick Check:

   AppModule organizes components and imports [OK]

Hint: AppModule declares components and imports modules [OK]

Common Mistakes:

• Confusing AppModule with styling or HTTP handling
• Thinking AppModule only manages routing
• Assuming AppModule is for CSS or HTTP only

2. Which of the following is the correct way to define the bootstrap property in @NgModule for starting the app with AppComponent?

easy

A. bootstrap: AppComponent

B. bootstrap = AppComponent

C. bootstrap = [AppComponent]

D. bootstrap: [AppComponent]

Solution

1. Step 1: Recall the syntax for bootstrap in @NgModule

   The bootstrap property expects an array of components to start the app.

2. Step 2: Match the correct syntax

   Using bootstrap: [AppComponent] is the correct way to provide an array with the main component.

3. Final Answer:

   bootstrap: [AppComponent] -> Option D

4. Quick Check:

   Bootstrap uses array syntax [OK]

Hint: Bootstrap needs an array of components [OK]

Common Mistakes:

• Using assignment (=) instead of colon (:)
• Not wrapping component in an array
• Omitting brackets around AppComponent

3. Given this AppModule snippet, what will happen when the app starts?

import { NgModule } from '@angular/core';
import { BrowserModule } from '@angular/platform-browser';
import { AppComponent } from './app.component';

@NgModule({
  declarations: [AppComponent],
  imports: [BrowserModule],
  bootstrap: [AppComponent]
})
export class AppModule { }

medium

A. The app will throw a syntax error

B. The app will fail because BrowserModule is missing

C. The app will start and display the AppComponent template

D. The app will start but show a blank page

Solution

1. Step 1: Check declarations and imports

   AppComponent is declared and BrowserModule is imported, which is required for browser apps.

2. Step 2: Verify bootstrap property

   AppComponent is bootstrapped correctly, so it will be the starting component shown.

3. Final Answer:

   The app will start and display the AppComponent template -> Option C

4. Quick Check:

   Proper declarations, imports, and bootstrap means app runs [OK]

Hint: Check declarations, imports, and bootstrap for app start [OK]

Common Mistakes:

• Assuming BrowserModule is missing
• Thinking bootstrap array can be empty
• Confusing syntax errors with correct code

4. Identify the error in this AppModule code:

@NgModule({
  declarations: AppComponent,
  imports: [BrowserModule],
  bootstrap: [AppComponent]
})
export class AppModule { }

medium

A. imports should not include BrowserModule

B. declarations should be an array, not a single component

C. bootstrap should not be an array

D. Missing import statement for AppComponent

Solution

1. Step 1: Check declarations syntax

   Declarations must be an array of components, but here it is a single component without brackets.

2. Step 2: Confirm other parts are correct

   Imports and bootstrap are correctly formatted; import statement is assumed present.

3. Final Answer:

   declarations should be an array, not a single component -> Option B

4. Quick Check:

   Declarations require array syntax [OK]

Hint: Declarations always use arrays [OK]

Common Mistakes:

• Forgetting brackets around declarations
• Confusing imports with declarations
• Thinking bootstrap cannot be an array

5. You want to add a new component HeaderComponent to your Angular app. Which changes must you make in AppModule to include it properly?

hard

A. Add HeaderComponent to declarations array and import its file

B. Add HeaderComponent only to bootstrap array

C. Add HeaderComponent to imports array

D. No changes needed if HeaderComponent is in the same folder

Solution

1. Step 1: Import the new component

   You must import HeaderComponent from its file to use it in AppModule.

2. Step 2: Declare the component in declarations array

   Adding HeaderComponent to declarations lets Angular recognize and use it in templates.

3. Final Answer:

   Add HeaderComponent to declarations array and import its file -> Option A

4. Quick Check:

   New components require import and declaration [OK]

Hint: Import and declare new components in AppModule [OK]

Common Mistakes:

• Adding component to imports instead of declarations
• Only adding to bootstrap instead of declarations
• Assuming no changes needed for new components