Optional providers in NestJS - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when an optional provider is not registered?

In NestJS, if a service is injected as an optional provider but is not registered in the module, what will be the value of the injected dependency inside the consuming class?

NestJS

import { Injectable, Optional } from '@nestjs/common';

@Injectable()
export class ConsumerService {
  constructor(@Optional() private readonly optionalService?: OptionalService) {}

  getStatus() {
    return this.optionalService ? 'Service available' : 'Service missing';
  }
}

// Assume OptionalService is NOT provided in any module

A The constructor will not be called because of missing provider

B 'Service available' because NestJS creates a default instance automatically

C Throws a runtime error due to missing provider

D 'Service missing' because the optional provider is undefined when not registered

💡 Hint

Think about what @Optional() decorator does when the provider is missing.

The @Optional() decorator tells NestJS that the provider might not be registered. If it is missing, NestJS injects undefined instead of throwing an error. So the injected dependency will be undefined, making the condition false and returning 'Service missing'.

📝 Syntax

intermediate

Identify the correct syntax to mark a provider as optional in NestJS

Which of the following constructor parameter declarations correctly marks a provider as optional in NestJS?

NestJS

import { Injectable, Optional } from '@nestjs/common';

@Injectable()
export class ExampleService {
  constructor( /* ??? */ ) {}
}

A constructor(@Optional() private readonly service: SomeService) {}

B constructor(private readonly service: @Optional() SomeService) {}

C constructor(private readonly @Optional() service: SomeService) {}

D constructor(private readonly service?: SomeService) {}

💡 Hint

Look at how decorators are placed before parameters in TypeScript.

The @Optional() decorator must be placed immediately before the parameter it decorates. Option A correctly places it before the parameter declaration. Options A and C have invalid syntax. Option A uses TypeScript optional parameter syntax but does not mark the provider as optional for NestJS.

❓ state_output

advanced

What is the output when an optional provider is injected and used?

Given the following NestJS service and module setup, what will be the output of the method call consumer.getMessage()?

NestJS

import { Injectable, Optional } from '@nestjs/common';

@Injectable()
export class OptionalService {
  getMessage() {
    return 'Hello from OptionalService';
  }
}

@Injectable()
export class ConsumerService {
  constructor(@Optional() private readonly optionalService?: OptionalService) {}

  getMessage() {
    return this.optionalService?.getMessage() ?? 'No service available';
  }
}

// Module setup:
// @Module({
//   providers: [ConsumerService] // OptionalService is NOT provided
// })

A 'Hello from OptionalService'

B Throws a runtime error because optionalService is undefined

C 'No service available'

D Returns undefined

💡 Hint

Check how the optionalService is used with optional chaining and fallback.

The optionalService is not provided, so it is undefined. The method uses optional chaining ?. to safely call getMessage() only if the service exists. Since it doesn't, the fallback string 'No service available' is returned.

🔧 Debug

advanced

Why does this optional provider injection cause a runtime error?

Consider this NestJS service constructor:

constructor(@Optional() private readonly service: SomeService) {}

If SomeService is not provided in any module, why might this code still cause a runtime error?

NestJS

import { Injectable, Optional } from '@nestjs/common';

@Injectable()
export class ConsumerService {
  constructor(@Optional() private readonly service: SomeService) {
    console.log(this.service.getName());
  }
}

A Because service is undefined and calling getName() on undefined causes a runtime error

B Because @Optional() decorator is missing

C Because NestJS always throws error if provider is missing regardless of @Optional()

D Because the constructor is missing the @Inject decorator

💡 Hint

Think about what happens when you call a method on undefined in JavaScript.

The @Optional() decorator makes NestJS inject undefined if the provider is missing. The constructor then tries to call getName() on undefined, which causes a runtime error: TypeError: Cannot read property 'getName' of undefined.

🧠 Conceptual

expert

How does NestJS resolve optional providers during dependency injection?

Which statement best describes how NestJS handles optional providers when resolving dependencies?

A NestJS throws an error if the provider is not registered, even if marked optional

B NestJS injects undefined for optional providers if they are not registered, allowing the consumer to handle absence gracefully

C NestJS injects a default instance of the provider if it is not registered, ensuring no errors occur

D NestJS skips the constructor parameter entirely if the provider is optional and missing

💡 Hint

Consider what @Optional() means for dependency injection behavior.

When a provider is marked with @Optional() and is not registered, NestJS injects undefined instead of throwing an error. This allows the consuming class to check for the provider's presence and handle its absence gracefully.