Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Apprendre How Providers Work in Nest.js | Section
Building Backend Applications with Nest.js

How Providers Work in Nest.js

Glissez pour afficher le menu

Previously, you learned that Nest.js can inject dependencies automatically. But how does Nest.js know which classes it can create?

To make a class available for dependency injection, you mark it with the @Injectable() decorator.

@Injectable()
export class UsersService {}

Next, register the service inside a module using the providers array.

@Module({
  providers: [UsersService],
})

Here is what is happening:

  • @Injectable() tells Nest.js that the class can be managed by the framework;
  • providers registers the service with the module;
  • Nest.js creates a single instance of the service;
  • Whenever another class requests UsersService, Nest.js provides the same instance automatically.

For example, the controller can now receive the service through its constructor:

constructor(private usersService: UsersService) {}

This system keeps your application organized by allowing different parts of your code to work together without manually creating or managing objects.

Tout était clair ?

Comment pouvons-nous l'améliorer ?

Merci pour vos commentaires !

Section 1. Chapitre 13

Demandez à l'IA

expand

Demandez à l'IA

ChatGPT

Posez n'importe quelle question ou essayez l'une des questions suggérées pour commencer notre discussion

Section 1. Chapitre 13
some-alt