Environment-based configuration in NestJS - Step-by-Step Execution

Concept Flow - Environment-based configuration

Start Application

↓

Load .env file

↓

Parse environment variables

↓

Inject ConfigService

↓

Access variables via ConfigService

↓

Use config values in app modules

↓

App runs with environment config

The app loads environment variables from a file, parses them, and makes them available via a service for use in modules.

Execution Sample

NestJS

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

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

// Usage in service
constructor(private configService: ConfigService) {}
const port = this.configService.get('PORT');

This code loads environment variables and accesses the PORT variable via ConfigService.

Execution Table

Step	Action	Result	Notes
1	Start app	App starts	Application bootstrap begins
2	ConfigModule.forRoot() loads .env	Environment variables loaded	Variables like PORT=3000 read
3	ConfigService injected in constructor	ConfigService instance ready	Can access env variables
4	Call configService.get('PORT')	Returns '3000'	Reads PORT from environment
5	Use PORT value in app	App listens on port 3000	App configured by env variable
6	App runs with env config	App fully running	Environment config applied

💡 App runs with environment variables loaded and accessible via ConfigService

Variable Tracker

Variable	Start	After Load .env	After Inject ConfigService	After get('PORT')	Final
process.env.PORT	undefined	3000	3000	3000	3000
configService	undefined	undefined	instance created	instance created	instance created
port	undefined	undefined	undefined	3000	3000

Key Moments - 3 Insights

Why do we need ConfigModule.forRoot()?

ConfigModule.forRoot() loads the .env file and sets environment variables before the app uses them, as shown in step 2 of the execution_table.

How does ConfigService get environment variables?

ConfigService reads variables from process.env after ConfigModule loads them, demonstrated in step 4 where get('PORT') returns '3000'.

What happens if .env file is missing?

If .env is missing, process.env variables may be undefined, so configService.get('PORT') would return undefined, causing app config issues.

Visual Quiz - 3 Questions

Look at the execution_table, what value does configService.get('PORT') return at step 4?

A '3000'

B 'undefined'

C 'null'

D '5000'

💡 Hint

Check the 'Result' column in row for step 4 in execution_table

At which step does the .env file get loaded into environment variables?

A Step 1

B Step 2

C Step 3

D Step 5

💡 Hint

Look for the step mentioning ConfigModule.forRoot() loading .env in execution_table

If the .env file is missing, what will configService.get('PORT') most likely return?

A '0'

B '3000'

C 'undefined'

D 'error thrown'

💡 Hint

Refer to key_moments about missing .env and variable values in variable_tracker

Concept Snapshot

Environment-based configuration in NestJS:
- Use ConfigModule.forRoot() to load .env variables
- Inject ConfigService to access variables
- Call configService.get('VAR_NAME') to read values
- Variables come from process.env after loading
- Enables flexible app config without code changes

Full Transcript

This visual trace shows how NestJS loads environment variables using ConfigModule.forRoot(), which reads the .env file and sets variables in process.env. Then, ConfigService is injected into classes to access these variables via the get() method. For example, calling configService.get('PORT') returns the port number defined in .env. The app uses this value to configure itself. If the .env file is missing, variables will be undefined, so the app must handle that case. This approach lets you change app settings without changing code, just by editing environment files.

Practice

1. What is the main purpose of using environment-based configuration in a NestJS application?

easy

A. To write more complex code logic

B. To hardcode all secrets inside the source files

C. To increase the size of the application

D. To change app settings without modifying the code

Solution

1. Step 1: Understand environment-based configuration

   It allows changing settings like database URLs or API keys without changing the app code.

2. Step 2: Identify the correct purpose

   Changing settings without code changes helps adapt the app to different environments easily.

3. Final Answer:

   To change app settings without modifying the code -> Option D

4. Quick Check:

   Environment config = change settings without code [OK]

Hint: Think: config changes without touching code [OK]

Common Mistakes:

• Confusing config with code logic
• Assuming config increases app size
• Hardcoding secrets inside source files

2. Which NestJS module is used to load environment variables for configuration?

easy

A. ConfigModule

B. DatabaseModule

C. HttpModule

D. LoggerModule

Solution

1. Step 1: Recall NestJS modules for config

   The ConfigModule is designed to load and manage environment variables.

2. Step 2: Match module to purpose

   HttpModule handles HTTP, DatabaseModule handles DB, LoggerModule handles logs, so ConfigModule is correct.

3. Final Answer:

   ConfigModule -> Option A

4. Quick Check:

   ConfigModule loads env variables [OK]

Hint: ConfigModule = environment variables loader [OK]

Common Mistakes:

• Choosing unrelated modules like HttpModule
• Confusing ConfigModule with DatabaseModule
• Assuming LoggerModule manages config

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 the environment variable DATABASE_HOST is set to localhost?

medium

A. DATABASE_HOST

B. undefined

C. localhost

D. null

Solution

1. Step 1: Understand ConfigService.get()

   This method returns the value of the environment variable key passed, here 'DATABASE_HOST'.

2. Step 2: Check environment variable value

   The variable DATABASE_HOST is set to 'localhost', so get() returns 'localhost'.

3. Final Answer:

   localhost -> Option C

4. Quick Check:

   ConfigService.get('DATABASE_HOST') = 'localhost' [OK]

Hint: ConfigService.get returns env var value [OK]

Common Mistakes:

• Expecting the key name instead of its value
• Assuming undefined if variable exists
• Confusing null with undefined

4. You wrote this code to load environment variables in NestJS:

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

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

But your app crashes with an error saying environment variables are undefined. What is the likely cause?

medium

A. You must call ConfigService.get() inside main.ts only

B. You forgot to create a .env file or set environment variables

C. You need to import HttpModule as well

D. ConfigModule.forRoot() should be called inside a service, not module

Solution

1. Step 1: Check environment variable source

   ConfigModule loads variables from .env file or system environment. If missing, variables are undefined.

2. Step 2: Identify common mistake

   Not having a .env file or not setting variables causes undefined values and app crash.

3. Final Answer:

   You forgot to create a .env file or set environment variables -> Option B

4. Quick Check:

   Missing .env file = undefined env vars [OK]

Hint: Always create .env file or set env vars [OK]

Common Mistakes:

• Thinking ConfigModule.forRoot() is misplaced
• Assuming HttpModule is needed for config
• Calling ConfigService.get() only in main.ts

5. You want to load different database URLs for development and production in NestJS using environment variables. Which approach correctly uses ConfigModule to load .env.development or .env.production based on NODE_ENV?

hard

A. ConfigModule.forRoot({ envFilePath: `.env.${process.env.NODE_ENV}` })

B. ConfigModule.forRoot({ envFilePath: '.env' })

C. ConfigModule.forRoot({ envFilePath: '.env.production' }) always

D. ConfigModule.forRoot({ envFilePath: '.env.development' }) always

Solution

1. Step 1: Understand dynamic env file loading

   Using envFilePath with template string allows loading .env files based on NODE_ENV value.

2. Step 2: Check options

   ConfigModule.forRoot({ envFilePath: `.env.${process.env.NODE_ENV}` }) dynamically loads .env.development or .env.production depending on NODE_ENV, others load fixed files.

3. Final Answer:

   ConfigModule.forRoot({ envFilePath: `.env.${process.env.NODE_ENV}` }) -> Option A

4. Quick Check:

   Dynamic envFilePath = correct multi-env config [OK]

Hint: Use template string with NODE_ENV for envFilePath [OK]

Common Mistakes:

• Hardcoding envFilePath to one file always
• Not using process.env.NODE_ENV in path
• Assuming default .env handles all environments