Root module (AppModule) in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the core NestJS module decorator.

NestJS

import { [1] } from '@nestjs/common';

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

AModule

BController

CInjectable

DService

Attempts:

3 left

💡 Hint

Common Mistakes

Using Controller or Injectable instead of Module

Forgetting to import the decorator

The @Module decorator is used to define a NestJS module like AppModule.

2fill in blank

medium

Complete the code to define the root module class named AppModule.

NestJS

@Module({})
export class [1] {}

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

AMainModule

BCoreModule

CRootModule

DAppModule

Attempts:

3 left

💡 Hint

Common Mistakes

Using other names like MainModule or RootModule

Not exporting the class

The root module class is conventionally named AppModule in NestJS projects.

3fill in blank

hard

Fix the error in the module decorator to include an empty imports array.

NestJS

@Module({ imports: [1] })
export class AppModule {}

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

A{}

Bnull

C[]

Dundefined

Attempts:

3 left

💡 Hint

Common Mistakes

Using null or undefined instead of an empty array

Omitting the imports property

The imports property expects an array, even if empty, to list imported modules.

4fill in blank

hard

Fill both blanks to add a controller and a provider to the module metadata.

NestJS

@Module({
  controllers: [[1]],
  providers: [[2]]
})
export class AppModule {}

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

AAppController

BAppService

CMainController

DMainService

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing controllers and providers

Using undefined names

The controllers array lists controllers like AppController, and providers lists services like AppService.

5fill in blank

hard

Fill all three blanks to import a module, add a controller, and add a provider in AppModule.

NestJS

import { Module } from '@nestjs/common';
import { [1] } from './cats/cats.module';
import { [2] } from './cats/cats.controller';
import { [3] } from './cats/cats.service';

@Module({
  imports: [[1]],
  controllers: [[2]],
  providers: [[3]]
})
export class AppModule {}

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

ACatsModule

BCatsController

CCatsService

DCatsProvider

Attempts:

3 left

💡 Hint

Common Mistakes

Using CatsProvider which does not exist

Mixing up controller and service names

To organize features, import CatsModule, add CatsController to controllers, and CatsService to providers.

Practice

1. What is the main purpose of the AppModule in a NestJS application?

easy

A. It serves as the root module that organizes controllers, providers, and imports.

B. It handles HTTP requests directly without controllers.

C. It is used only for database connections.

D. It runs background tasks without user interaction.

Solution

1. Step 1: Understand the role of AppModule

   The AppModule is the root module that organizes the app's structure by grouping controllers, providers, and imports.

2. Step 2: Compare with other options

   Options A, B, and D describe specific tasks that are handled by other parts of the app, not the root module itself.

3. Final Answer:

   It serves as the root module that organizes controllers, providers, and imports. -> Option A

4. Quick Check:

   Root module = organizes app parts [OK]

Hint: AppModule organizes app parts as root module [OK]

Common Mistakes:

• Thinking AppModule handles requests directly
• Confusing AppModule with service or controller
• Assuming AppModule is only for database setup

2. Which of the following is the correct way to define the AppModule using the @Module decorator in NestJS?

easy

A. @Module({ controllers: [], providers: [] }) export class AppModule {}

B. export class AppModule {}

C. @Module({ controllers: [], providers: [] }) class AppModule {}

D. class AppModule {}

Solution

1. Step 1: Recognize correct @Module syntax

   The @Module decorator requires an object with properties like controllers and providers, and must decorate an exported class.

2. Step 2: Check each option

   @Module({ controllers: [], providers: [] }) export class AppModule {} correctly uses @Module with an object and exports the class. Options B and D lack the decorator, and C misses export keyword.

3. Final Answer:

   @Module({ controllers: [], providers: [] }) export class AppModule {} -> Option A

4. Quick Check:

   @Module + export class = correct syntax [OK]

Hint: Use @Module decorator with export class [OK]

Common Mistakes:

• Forgetting to export the AppModule class
• Missing the @Module decorator
• Not passing an object to @Module

3. Given this AppModule code, what will be the output when the app starts?

import { Module } from '@nestjs/common';
import { CatsController } from './cats.controller';
import { CatsService } from './cats.service';

@Module({
  controllers: [CatsController],
  providers: [CatsService],
})
export class AppModule {}

medium

A. The app starts but CatsService is not available.

B. The app throws an error because providers are missing.

C. The app starts but CatsController is not registered.

D. The app starts with CatsController and CatsService registered.

Solution

1. Step 1: Analyze the @Module configuration

   The AppModule imports CatsController in controllers and CatsService in providers, so both are registered properly.

2. Step 2: Understand NestJS app startup

   With both controller and provider registered, the app starts normally with these components available.

3. Final Answer:

   The app starts with CatsController and CatsService registered. -> Option D

4. Quick Check:

   Controllers and providers registered = app starts [OK]

Hint: Controllers and providers in @Module start app correctly [OK]

Common Mistakes:

• Assuming missing imports cause errors here
• Thinking providers are optional for controllers
• Confusing registration with usage

4. Identify the error in this AppModule code snippet:

import { Module } from '@nestjs/common';

@Module({
  controllers: CatsController,
  providers: [CatsService],
})
export class AppModule {}

medium

A. AppModule class should not be exported.

B. Controllers should be an array, not a single value.

C. Missing import statement for CatsService.

D. Providers should be an object, not an array.

Solution

1. Step 1: Check the controllers property type

   The controllers property must be an array, but here it is assigned a single value CatsController without brackets.

2. Step 2: Verify other parts

   Providers are correctly an array. Import statements are not shown but assumed correct. Exporting AppModule is correct.

3. Final Answer:

   Controllers should be an array, not a single value. -> Option B

4. Quick Check:

   Controllers must be array [OK]

Hint: Controllers and providers must be arrays [OK]

Common Mistakes:

• Using single controller without array brackets
• Confusing providers array with object
• Forgetting to export AppModule

5. You want to add a new feature module called UsersModule to your NestJS app. How should you modify the AppModule to include it properly?

hard

A. Add UsersModule to the controllers array in @Module decorator.

B. Add UsersModule to the providers array in @Module decorator.

C. Add UsersModule to the imports array in @Module decorator.

D. Create a new AppModule inside UsersModule.

Solution

1. Step 1: Understand module composition in NestJS

   Feature modules like UsersModule are imported into the root module via the imports array to connect them.

2. Step 2: Evaluate options

   Controllers and providers arrays are for specific controllers and services, not modules. Creating a new AppModule inside UsersModule is incorrect structure.

3. Final Answer:

   Add UsersModule to the imports array in @Module decorator. -> Option C

4. Quick Check:

   Feature modules go in imports [OK]

Hint: Add feature modules to imports array [OK]

Common Mistakes:

• Adding modules to controllers or providers
• Creating multiple AppModules
• Forgetting to import feature modules