Node.js / NestJS

Configuration & Environment Management

ConfigModule, environment variables, .env, secrets, multi-env (dev/staging/prod), feature flags

20 Interview-Fragen·
Mid-Level
1

What is the ConfigModule in NestJS?

Antwort

ConfigModule is an official NestJS module that centralizes application configuration management. It allows loading environment variables from .env files, validating them with schemas, and injecting them into services via ConfigService. Unlike direct access to process.env, it provides strong typing and facilitates unit testing.

2

How to import ConfigModule in a NestJS application?

Antwort

ConfigModule is imported with ConfigModule.forRoot() in the root module (AppModule). This method automatically loads the .env file from the project root and makes ConfigService globally available. It's also possible to pass options like envFilePath to specify a custom path or isGlobal to avoid reimporting the module.

3

What is the role of the .env file in a Node.js application?

Antwort

The .env file stores environment-specific variables for each environment (development, staging, production). It contains values like database URLs, API keys, and secrets. This file should never be committed to Git (added to .gitignore) to avoid exposing sensitive information. It's loaded at startup via libraries like dotenv.

4

How to access an environment variable with ConfigService?

5

Which library does NestJS use to load .env files?

+17 Interview-Fragen

Meistere Node.js / NestJS für dein nächstes Interview

Zugang zu allen Fragen, Flashcards, technischen Tests, Code-Review-Übungen und Interview-Simulatoren.

Kostenlos starten