Module decorator and metadata in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a NestJS module with the @Module decorator.

NestJS

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

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

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

Aimports

Bcomponents

Cservices

Dcontrollers

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'components' or 'services' which are not valid properties in @Module.

Confusing 'controllers' with 'imports'.

The @Module decorator uses the imports property to specify modules to import.

2fill in blank

medium

Complete the code to add a controller to the module metadata.

NestJS

@Module({
  controllers: [[1]],
})
export class UserModule {}

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

AUserEntity

BUserService

CAppModule

DUserController

Attempts:

3 left

💡 Hint

Common Mistakes

Putting services or entities inside the controllers array.

Confusing controller with service names.

The controllers array should list controller classes like UserController.

3fill in blank

hard

Fix the error in the module metadata by completing the providers array correctly.

NestJS

@Module({
  providers: [[1]],
})
export class AuthModule {}

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

AAuthModule

BAuthController

CAuthService

DAuthEntity

Attempts:

3 left

💡 Hint

Common Mistakes

Adding controllers or modules to providers array.

Confusing entities with providers.

The providers array should include service classes like AuthService that provide functionality.

4fill in blank

hard

Fill both blanks to complete the module metadata with imports and exports.

NestJS

@Module({
  [1]: [CommonModule],
  [2]: [CommonModule],
})
export class SharedModule {}

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

Aimports

Bproviders

Cexports

Dcontrollers

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up exports with providers or controllers.

Using providers instead of exports to share modules.

The imports array brings in modules, and exports makes them available to other modules.

5fill in blank

hard

Fill all three blanks to complete a module with imports, controllers, and providers.

NestJS

@Module({
  [1]: [DatabaseModule],
  [2]: [AppController],
  [3]: [AppService],
})
export class AppModule {}

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

Aimports

Bcontrollers

Cproviders

Dexports

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping controllers and providers.

Putting modules in providers or controllers.

The imports array includes other modules, controllers lists controllers, and providers lists services.