ConfigModule setup in NestJS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import ConfigModule globally in a NestJS module.

NestJS

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

@Module({
  imports: [ConfigModule.[1]({ isGlobal: true })],
})
export class AppModule {}

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

AforRoot

Bregister

Ccreate

Dinitialize

Attempts:

3 left

💡 Hint

Common Mistakes

Using a method name that does not exist on ConfigModule.

Forgetting to set isGlobal to true for global availability.

The ConfigModule.forRoot() method is used to set up the configuration module globally in NestJS.

2fill in blank

medium

Complete the code to load a custom configuration file using ConfigModule.

NestJS

import { Module } from '@nestjs/common';
import { ConfigModule } from '@nestjs/config';
import customConfig from './custom.config';

@Module({
  imports: [ConfigModule.forRoot({ [1]: [customConfig] })],
})
export class AppModule {}

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

AconfigFiles

Bfiles

Cimports

Dload

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect option names like 'files' or 'imports'.

Passing the configuration file directly without wrapping in an array.

The load option allows you to provide custom configuration files or functions to the ConfigModule.

3fill in blank

hard

Fix the error in the code to correctly inject ConfigService in a service constructor.

NestJS

import { Injectable } from '@nestjs/common';
import { ConfigService } from '@nestjs/config';

@Injectable()
export class MyService {
  constructor(private readonly [1]: ConfigService) {}
}

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

AconfigService

Bservice

CConfigService

Dconfig

Attempts:

3 left

💡 Hint

Common Mistakes

Using the class name as the parameter name.

Using generic or unclear parameter names.

The parameter name in the constructor should be camelCase, typically configService, to follow NestJS conventions and avoid confusion.

4fill in blank

hard

Fill both blanks to create a configuration object with environment variables and default values.

NestJS

export default () => ({
  port: parseInt(process.env.[1] || '[2]', 10),
});

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

APORT

B3000

CNODE_PORT

D8080

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect environment variable names.

Not providing a string default value.

The environment variable PORT is commonly used for the server port, and 3000 is a typical default port number.

5fill in blank

hard

Fill all three blanks to access a nested configuration value safely using ConfigService.

NestJS

const dbHost = this.configService.get<string>('database.[1].[2]', [3]);

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

Aconnection

Bhost

C'localhost'

Dport

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect nested keys.

Using an options object instead of a positional default value.

The nested keys connection and host access the database host, and 'localhost' provides a fallback if the key is missing.

Practice

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

easy

A. To manage application settings using environment variables

B. To handle HTTP requests and responses

C. To connect to a database

D. To create middleware for logging

Solution

1. Step 1: Understand ConfigModule role

   The ConfigModule is designed to load and manage configuration settings, often from environment variables.

2. Step 2: Compare with other options

   Options A, B, and D relate to other parts of NestJS like database connections, HTTP handling, and middleware, not configuration management.

3. Final Answer:

   To manage application settings using environment variables -> Option A

4. Quick Check:

   ConfigModule = Manage app settings [OK]

Hint: ConfigModule is for app settings, not HTTP or DB [OK]

Common Mistakes:

• Confusing ConfigModule with database modules
• Thinking ConfigModule handles HTTP requests
• Assuming ConfigModule creates middleware

2. Which is the correct way to import ConfigModule globally in the root module?

easy

A. ConfigModule.register({ global: true })

B. ConfigModule.forFeature({ isGlobal: true })

C. ConfigModule.forRoot({ isGlobal: true })

D. ConfigModule.global()

Solution

1. Step 1: Recall ConfigModule global setup syntax

   To make ConfigModule available app-wide, use forRoot() with isGlobal: true.

2. Step 2: Check other options for correctness

   forFeature() is for scoped configs, register() and global() are not valid methods here.

3. Final Answer:

   ConfigModule.forRoot({ isGlobal: true }) -> Option C

4. Quick Check:

   Global config = forRoot + isGlobal true [OK]

Hint: Use forRoot with isGlobal true for global config [OK]

Common Mistakes:

• Using forFeature instead of forRoot
• Trying to use non-existent methods like global()
• Confusing register with forRoot

3. Given this code snippet in a NestJS service:

constructor(private configService: ConfigService) {}

getDbHost() {
  return this.configService.get('DATABASE_HOST');
}

What will getDbHost() return if DATABASE_HOST is set to "localhost" in the environment?

medium

A. Throws an error

B. undefined

C. null

D. "localhost"

Solution

1. Step 1: Understand ConfigService.get behavior

   The get method returns the value of the environment variable if set, here 'localhost'.

2. Step 2: Check environment variable presence

   Since DATABASE_HOST is set to 'localhost', the method returns that string, not undefined or null.

3. Final Answer:

   "localhost" -> Option D

4. Quick Check:

   Env var set = get returns value [OK]

Hint: get() returns env value if set, else undefined [OK]

Common Mistakes:

• Assuming get returns null if variable exists
• Expecting an error if variable is missing
• Confusing undefined with null

4. Identify the error in this NestJS module setup:

@Module({
  imports: [ConfigModule.forRoot({ isGlobal: true })],
  providers: [ConfigService],
})
export class AppModule {}

medium

A. ConfigService should not be listed in providers when ConfigModule is global

B. Missing import of ConfigService from '@nestjs/config'

C. forRoot() should not have isGlobal option

D. ConfigModule should be imported in controllers, not imports

Solution

1. Step 1: Understand global ConfigModule behavior

   When isGlobal: true is set, ConfigService is automatically provided app-wide, no need to add it manually.

2. Step 2: Check other options for validity

   Importing ConfigService is not mandatory in module file, forRoot supports isGlobal, and ConfigModule belongs in imports array.

3. Final Answer:

   ConfigService should not be listed in providers when ConfigModule is global -> Option A

4. Quick Check:

   Global ConfigModule auto-provides ConfigService [OK]

Hint: Don't add ConfigService to providers if ConfigModule is global [OK]

Common Mistakes:

• Adding ConfigService to providers unnecessarily
• Thinking isGlobal is invalid option
• Placing ConfigModule in controllers array

5. You want to load a custom configuration file named custom.env using ConfigModule and make it global. Which setup is correct?

hard

A. ConfigModule.forRoot({ envFileName: 'custom.env', global: true })

B. ConfigModule.forRoot({ envFilePath: 'custom.env', isGlobal: true })

C. ConfigModule.forFeature({ envFilePath: 'custom.env', isGlobal: true })

D. ConfigModule.register({ envFilePath: 'custom.env', isGlobal: true })

Solution

1. Step 1: Identify correct option names for ConfigModule

   The correct option to specify a custom env file is envFilePath, and to make it global use isGlobal: true inside forRoot().

2. Step 2: Eliminate incorrect options

   envFileName and global are invalid option names; forFeature and register are not used for global config loading.

3. Final Answer:

   ConfigModule.forRoot({ envFilePath: 'custom.env', isGlobal: true }) -> Option B

4. Quick Check:

   Custom env + global = envFilePath + isGlobal true [OK]

Hint: Use envFilePath and isGlobal in forRoot for custom global config [OK]

Common Mistakes:

• Using envFileName instead of envFilePath
• Trying to use forFeature for global config
• Using register instead of forRoot