Multiple Injectables with nestjs-modules about nestjs HOT 2 CLOSED

Looking further into this I feel like if your goal is to have multiple injectables provided from your dynamic module that the current APIs support that relatively easily. The boilerplate that this library removes is for the configuration of your Dynamic Module, not for what it will provide. So in that sense you can pass as complex an object as you want under one Injection token for the configuration.

Check out this snippet from the RabbitMQ library:

export class RabbitMQModule
  extends createConfigurableDynamicRootModule<RabbitMQModule, RabbitMQConfig>(
    RABBIT_CONFIG_TOKEN,
    {
      providers: [
        {
          provide: AmqpConnection,
          useFactory: async (
            config: RabbitMQConfig
          ): Promise<AmqpConnection> => {
            const connection = new AmqpConnection(config);
            await connection.init();
            const logger = new Logger(RabbitMQModule.name);
            logger.log('Successfully connected to RabbitMQ');
            return connection;
          },
          inject: [RABBIT_CONFIG_TOKEN]
        }
      ],
      exports: [AmqpConnection]
    }
  )

You can see that it has one provider which is implemented with a factory function which relies on the Config object (in this case RabbitMQConfig) to build up and provide an AmqpConnection.

If the config object for this dynamic module were more complex (with multiple top level object keys that each were responsible for configuring an individual provider), I could easily add more providers to the array in the above snippet and have each of them return something else based on the Config object:

export class RabbitMQModule
  extends createConfigurableDynamicRootModule<RabbitMQModule, RabbitMQConfig>(
    RABBIT_CONFIG_TOKEN,
    {
      providers: [
        {
          provide: AmqpConnection,
          useFactory: async (
            config: RabbitMQConfig
          ): Promise<AmqpConnection> => {
            const connection = new AmqpConnection(config);
            await connection.init();
            const logger = new Logger(RabbitMQModule.name);
            logger.log('Successfully connected to RabbitMQ');
            return connection;
          },
          inject: [RABBIT_CONFIG_TOKEN]
        },
        {
          provide: AmqpConnection,
          useFactory: async (
            config: RabbitMQConfig
          ): Promise<SomeOtherThing> => {
            // do something with config
           return new SomeOtherThing();
          },
          inject: [RABBIT_CONFIG_TOKEN]
        }
      ],
      exports: [AmqpConnection]
    }
  )

I'm not sure I see the use case for needing to inject the configuration options to other places after the fact as generally it's simply used to bootstrap the dynamic module properly but you could easily inject the config object and then just access the property on it that you need eg options.service in your example or you could even use the snippets I've provided as a starting point to provide them dynamically using providers as a means of destructuring the top level config object into discrete parts each using it's own new Injectable token.

Let me know if this allows you to accomplish the scenario that you're after

from nestjs.

I made an example app so you can see it in action. You can pull it down and run it but the relevant files are here:

https://github.com/WonderPanda/dynamic-modules-example/blob/master/src/dynamic-example/dynamic-example.module.ts

https://github.com/WonderPanda/dynamic-modules-example/blob/master/src/app.module.ts

https://github.com/WonderPanda/dynamic-modules-example/blob/master/src/app.controller.ts

Feel free to re-open this if you feel this doesn't meet your needs

from nestjs.