Questions
9 of 11
1What is a provider in NestJS?
2What are the different forms of custom provider syntax in NestJS?
3How does NestJS handle async providers and what problem do they solve?
4What are provider scopes in NestJS and when would you change the default?
5How do you resolve a circular dependency between two providers in NestJS?
6Walk through all four custom provider types: useClass, useValue, useFactory, useExisting.
7How do you create a multi-provider pattern in NestJS to inject multiple implementations for the same token?
8How does an async provider work in NestJS and what guarantees does it give?
9What is the shorthand provider syntax in NestJS and what does it expand to?
10What is the difference between useExisting and useClass when aliasing a provider in NestJS?
11How do you make a provider accessible across the entire module graph using ModuleRef.get() with strict: false?
NestJSNestJS
Basics
Modules
Decorators
Controllers
Dependency Injection
Providers
Architecture
Request Lifecycle
Middleware
Guards
Interceptors
Pipes
Filters
Exception Handling
API Design
GraphQL
Database and ORM
Microservices
Authentication and Authorization
09 / 11

What is the shorthand provider syntax in NestJS and what does it expand to?

When you write a class name directly in the providers array, NestJS expands it to the full useClass form where the class is used as both the token and the implementation. This works because TypeScript emits metadata for class types so the container knows how to instantiate it.

Shorthand vs full provider form
When shorthand works and when it does not:
  1. 1

    Shorthand works only when the class itself is the token — the most common case.

  2. 2

    Use full form when providing an interface token, string token, or swapping implementation.

  3. 3

    Use full form when using useValue, useFactory, or useExisting.

  4. 4

    Shorthand is just syntactic sugar — both forms produce identical DI behavior.