使用@golevelup/nestjs-rabbitmq时Nest无法解析依赖的问题

我正在用@golevelup/nestjs-rabbitmq开发NestJS应用，用于向RabbitMQ交换机发送消息。已在AppModule中完成RabbitMQModule的导入和配置（该部分运行正常），但创建MessagingModule和MessagingService后，在MessagingService构造函数中注入AmqpConnection时出现以下错误：

错误信息：

error:  Nest can't resolve dependencies of the RabbitMQModule (DiscoveryService, ExternalContextCreator, ?, AmqpConnectionManager). Please make sure that the argument RabbitRpcParamsFactory at index [2] is available in the RabbitMQModule context.

Potential solutions:
- Is RabbitMQModule a valid NestJS module?
- If RabbitRpcParamsFactory is a provider, is it part of the current RabbitMQModule?
- If RabbitRpcParamsFactory is exported from a separate @Module, is that module imported within RabbitMQModule?

AppModule代码：

import { ConfigModule } from '@nestjs/config';
import { configuration } from './config/configuration';
import { MessagingModule } from './messaging/messaging.module';
import { RabbitMQModule } from '@golevelup/nestjs-rabbitmq';
import { ConfigService } from '@nestjs/config';

@Module({
  imports: [
    ConfigModule.forRoot({
      isGlobal: true,
      cache: true,
      load: [configuration],
      validationSchema,
      validationOptions: {
        allowUnknown: false,
        abortEarly: true,
      },
    }),
    RabbitMQModule.forRootAsync(RabbitMQModule, {
      imports: [ConfigModule],
      inject: [ConfigService],
      useFactory: async (configService: ConfigService) => ({
        exchanges: [
          {
            name: configService.get<string>('RABBITMQ_EXCHANGE'),
            type: configService.get<string>('RABBITMQ_EXCHANGE_TYPE'),
          },
        ],
        uri: configService.get<string>('RABBITMQ_URL'),
        channels: {
          'channel-1': {
            prefetchCount: 15,
            default: true,
          },
          'channel-2': {
            prefetchCount: 2,
          },
        },
        connectionInitOptions: { wait: false },
        enableControllerDiscovery: true,
      }),
    }),
    MessagingModule,
  ],
  controllers: [],
  providers: [],
})
export class AppModule {}

MessagingModule代码：

import { RabbitMQModule } from '@golevelup/nestjs-rabbitmq';
import { Module } from '@nestjs/common';
import { ConfigService } from '@nestjs/config';
import { MessagingService } from './messaging.service';
import { MessagingController } from './messaging.controller';

@Module({
  
  imports: [
    RabbitMQModule,
    MessagingModule,
  ],
  providers: [ConfigService, MessagingService],
  controllers: [MessagingController],
  exports: [MessagingService],
})
export class MessagingModule {}

MessagingService代码：

import { Injectable } from '@nestjs/common';
import { ConfigService } from '@nestjs/config';
import { AmqpConnection } from '@golevelup/nestjs-rabbitmq';

@Injectable()
export class MessagingService {
  constructor(private readonly amqpConnection: AmqpConnection) {}

  // Publish the event to the exchange
  public async publish<T>(exchange: string, event: T): Promise<void> {
    await this.amqpConnection.publish(exchange, '', event);
  }

}

问题原因及修复方案 #

核心问题 #

1. 循环导入：MessagingModule的imports数组中导入了自身MessagingModule，导致Nest无法正确解析模块依赖链，进而触发RabbitMQModule的依赖解析错误。
2. 重复声明全局服务：ConfigModule已设置为全局模块（isGlobal: true），其提供的ConfigService无需在MessagingModule的providers中重复声明。

修复步骤 #

修改MessagingModule代码，移除循环导入和重复的ConfigService声明：

import { RabbitMQModule } from '@golevelup/nestjs-rabbitmq';
import { Module } from '@nestjs/common';
import { MessagingService } from './messaging.service';
import { MessagingController } from './messaging.controller';

@Module({
  imports: [RabbitMQModule],
  providers: [MessagingService],
  controllers: [MessagingController],
  exports: [MessagingService],
})
export class MessagingModule {}

额外说明 #

• AppModule中通过RabbitMQModule.forRootAsync完成配置后，其他模块只需导入RabbitMQModule，即可获取AmqpConnection等服务的注入权限。
• 全局模块提供的服务可在任意模块中直接注入，无需重复导入或声明。

内容的提问来源于stack exchange，提问作者pengz