feature request: forRootAsync missing

[kastov]

Hi there!

Thanks for great package.

I planned to use it, but I did not found a way to inject ConfigService to provide Redis or RabbitMQ credentials.
Is it possible to do this now with forRootAsync or registerAsync option?

Like in this example:

CacheModule.registerAsync({
            imports: [ConfigModule],
            inject: [ConfigService],
            isGlobal: true,
            useFactory: async (configService: ConfigService) => {
                return {
                    stores: [
                        createKeyv(
                            {
                                url: `redis://${configService.getOrThrow<string>('REDIS_HOST')}:${configService.getOrThrow<number>('REDIS_PORT')}`,
                                database: configService.getOrThrow<number>('REDIS_DB'),
                                password: configService.get<string | undefined>('REDIS_PASSWORD'),
                            },
                        ),
                    ],
                };
            },
        })

[Sebastian-Iwanczyszyn]

Hey! Thanks for the kind words 😊

Injecting ConfigService via forRootAsync or registerAsync is definitely on my roadmap - I'm planning to support it in version 2.x!

In the meantime, as a workaround, you can use process.env.YOUR_ENV_VALUE directly, or create a simple Environment class where you assign values from your .env file to class properties. You can then use this class in your configuration logic.

// src/config/environment.ts

export class Environment {
  public static readonly REDIS_HOST: string = process.env.REDIS_HOST || 'localhost';
  public static readonly REDIS_PORT: number = parseInt(process.env.REDIS_PORT || '6379', 10);
  
  public static readonly RABBITMQ_URL: string = process.env.RABBITMQ_URL || 'amqp://localhost';
  public static readonly RABBITMQ_QUEUE: string = process.env.RABBITMQ_QUEUE || 'default_queue';

  // Add more environment-based configs as needed
}

This should work temporarily, but full async config support will be available in the near future.

[kastov]

Hey! Thanks for the kind words 😊

Injecting ConfigService via forRootAsync or registerAsync is definitely on my roadmap - I'm planning to support it in version 2.x!

In the meantime, as a workaround, you can use process.env.YOUR_ENV_VALUE directly, or create a simple Environment class where you assign values from your .env file to class properties. You can then use this class in your configuration logic.

// src/config/environment.ts

export class Environment {
public static readonly REDIS_HOST: string = process.env.REDIS_HOST || 'localhost';
public static readonly REDIS_PORT: number = parseInt(process.env.REDIS_PORT || '6379', 10);

public static readonly RABBITMQ_URL: string = process.env.RABBITMQ_URL || 'amqp://localhost';
public static readonly RABBITMQ_QUEUE: string = process.env.RABBITMQ_QUEUE || 'default_queue';

// Add more environment-based configs as needed
}
This should work temporarily, but full async config support will be available in the near future.

Hi again, sorry for ping.

Can you also check up PR nestjstools/messaging-redis-extension#2?

[Sebastian-Iwanczyszyn]

Small update:

In version 2.19.0 you can load MessagingModule.forRootAsync()

Here you got an example: https://github.com/nestjstools/messaging-rabbitmq-example/blob/main/src/app.module.ts#L24-L93
(Only channels need to be loaded in async way)

Also, you got a simple test in the repository of messaging with example TestAsyncModule

🙇 Thanks, I think we can close this topic, feature added.