Configuration namespaces in NestJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What is the output of accessing a nested configuration namespace?

Given a NestJS configuration service with namespaces, what will be the output of the following code?

NestJS

const config = new ConfigService({ database: { host: 'localhost', port: 5432 } });
const host = config.get('database.host');
console.log(host);

A undefined

B "database.host"

C "localhost"

D Throws an error

💡 Hint

Think about how nested keys are accessed in configuration namespaces.

The get method supports dot notation to access nested properties. So database.host returns the string "localhost".

📝 Syntax

intermediate

Which option correctly defines a configuration namespace in NestJS?

Choose the correct way to define a configuration namespace using registerAs in NestJS.

A registerAs('database', { host: 'localhost', port: 5432 });

B export const database = registerAs('database', () => ({ host: 'localhost', port: 5432 }));

C export const database = registerAs(() => ({ host: 'localhost', port: 5432 }));

D export default registerAs('database', () => ({ host: 'localhost', port: 5432 }));

💡 Hint

Remember that registerAs requires a name and a function returning the config object.

Option B correctly exports a constant assigned to registerAs with a name and a function returning the config object. Option B uses default export which is not typical. Option B misses the name argument. Option B passes an object instead of a function.

❓ state_output

advanced

What is the value of a nested config key after merging multiple namespaces?

Consider two configuration namespaces merged in NestJS. What is the value of app.port after merging?

NestJS

const appConfig = registerAs('app', () => ({ port: 3000, debug: true }));
const overrideConfig = registerAs('app', () => ({ port: 4000 }));

const configService = new ConfigService({
  ...appConfig(),
  ...overrideConfig()
});

const port = configService.get('port');
console.log(port);

A 4000

B 3000

C undefined

D Throws an error

💡 Hint

Think about how object spread works when merging objects with overlapping keys.

The second object overrideConfig() overwrites the port key from the first. So the final port is 4000.

🔧 Debug

advanced

Why does accessing a nested config key return undefined?

Given this code, why does config.get('database.password') return undefined?

NestJS

const config = new ConfigService({ database: { user: 'admin' } });
const password = config.get('database.password');
console.log(password);

A Because the config object is empty

B Because dot notation is not supported in get method

C Because ConfigService requires explicit schema for nested keys

D Because 'password' key does not exist in the 'database' namespace

💡 Hint

Check if the key you are accessing exists in the config object.

The password key is missing from the database object, so accessing it returns undefined. Dot notation is supported, and the config object is not empty.

🧠 Conceptual

expert

Which statement best describes configuration namespaces in NestJS?

Choose the most accurate description of how configuration namespaces work in NestJS.

A Namespaces group related config values and allow dot notation access, improving organization and type safety.

B Namespaces automatically validate config values against a schema without extra setup.

C Namespaces flatten all config keys into a single level object for easier access.

D Namespaces prevent any runtime changes to configuration values once loaded.

💡 Hint

Think about the purpose of namespaces and how they affect config access.

Namespaces in NestJS group related configuration values and support dot notation for easy access. They do not automatically validate or flatten keys, nor do they prevent runtime changes by default.

Practice

1. What is the main purpose of using registerAs in NestJS configuration?

easy

A. To create a database connection

B. To register a global middleware in the application

C. To define a new module in NestJS

D. To create a named namespace grouping related configuration settings

Solution

1. Step 1: Understand the role of registerAs

   registerAs is used to define a configuration namespace, grouping related settings under one name.

2. Step 2: Differentiate from other NestJS features

   It is not used for middleware, modules, or database connections, which are handled differently.

3. Final Answer:

   To create a named namespace grouping related configuration settings -> Option D

4. Quick Check:

   registerAs creates config namespaces = A [OK]

Hint: Remember: registerAs groups config keys under one name [OK]

Common Mistakes:

• Confusing registerAs with module registration
• Thinking registerAs sets up middleware
• Assuming registerAs creates database connections

2. Which of the following is the correct syntax to create a configuration namespace called 'database' using registerAs?

easy

A. export const database = registerAs('database', () => ({ host: 'localhost' }));

B. registerAs('database', { host: 'localhost' });

C. export default registerAs('database', () => ({ host: 'localhost' }));

D. registerAs('database', () => { host: 'localhost' });

Solution

1. Step 1: Check correct export and function syntax

   The correct pattern is to export a constant assigned to registerAs with a name and a function returning an object.

2. Step 2: Identify syntax errors in options

   export default registerAs('database', () => ({ host: 'localhost' })); uses default export but misses const assignment. registerAs('database', { host: 'localhost' }); passes object directly, not a function. registerAs('database', () => { host: 'localhost' }); misses returning an object (no parentheses).

3. Final Answer:

   export const database = registerAs('database', () => ({ host: 'localhost' })); -> Option A

4. Quick Check:

   Correct syntax = A [OK]

Hint: Use export const with registerAs and a function returning config [OK]

Common Mistakes:

• Passing object directly instead of function
• Missing export const declaration
• Not returning an object from the function

3. Given the following configuration namespace registered as 'app':

export const appConfig = registerAs('app', () => ({ port: 3000, env: 'dev' }));

What will configService.get('app.port') return?

medium

A. 3000

B. 'app.port'

C. undefined

D. An error is thrown

Solution

1. Step 1: Understand dot notation access in ConfigService

   Using configService.get('app.port') accesses the 'port' key inside the 'app' namespace.

2. Step 2: Check the registered config values

   The 'app' namespace returns an object with port: 3000, so the call returns 3000.

3. Final Answer:

   3000 -> Option A

4. Quick Check:

   configService.get('namespace.key') returns value = B [OK]

Hint: Use dot notation to get nested config values [OK]

Common Mistakes:

• Expecting the string 'app.port' as output
• Assuming undefined if namespace not accessed properly
• Thinking it throws an error for valid keys

4. Consider this code snippet:

export const apiConfig = registerAs('api', () => ({ url: 'https://api.example.com' }));

// Later in service
const url = configService.get('api.url');

What is the likely cause if url is undefined?

medium

A. The configService instance is not injected properly

B. The namespace 'api' was not imported or registered in ConfigModule

C. Dot notation is not supported in configService.get()

D. The key 'url' does not exist in the 'api' namespace

Solution

1. Step 1: Check registration of namespace

   If the 'api' namespace is not imported or registered in the ConfigModule, its keys won't be available.

2. Step 2: Verify key existence and usage

   The key 'url' exists in the namespace, and dot notation is supported, so these are not issues.

3. Step 3: Consider injection issues

   While injection problems can cause errors, they usually throw exceptions, not silently return undefined.

4. Final Answer:

   The namespace 'api' was not imported or registered in ConfigModule -> Option B

5. Quick Check:

   Missing namespace registration = D [OK]

Hint: Always import and register namespaces in ConfigModule [OK]

Common Mistakes:

• Assuming dot notation is unsupported
• Thinking missing key causes error instead of undefined
• Ignoring namespace registration step

5. You have two configuration namespaces registered:

export const dbConfig = registerAs('database', () => ({ host: 'localhost', port: 5432 }));
export const authConfig = registerAs('auth', () => ({ jwtSecret: 'secret' }));

How can you access the JWT secret inside a service using ConfigService and ensure type safety?

hard

A. const secret = configService.get<number>('auth.jwtSecret');

B. const secret = configService.get('jwtSecret');

C. const secret = configService.get<string>('auth.jwtSecret');

D. const secret = configService.get('database.jwtSecret');

Solution

1. Step 1: Use dot notation with namespace and key

   To access the JWT secret, use 'auth.jwtSecret' to specify the namespace and key.

2. Step 2: Apply type safety with generic parameter

   Pass <string> to get to ensure the returned value is typed as string.

3. Step 3: Eliminate incorrect options

   const secret = configService.get('jwtSecret'); misses namespace, A uses wrong type, D uses wrong namespace.

4. Final Answer:

   const secret = configService.get<string>('auth.jwtSecret'); -> Option C

5. Quick Check:

   Use namespace.key with type param = C [OK]

Hint: Use configService.get<Type>('namespace.key') for typed access [OK]

Common Mistakes:

• Omitting namespace in key string
• Using wrong type parameter
• Accessing key from wrong namespace