NestJS依赖注入报错：无法解析AuthService的第二个依赖，求解决

错误信息 #

[Nest] 12812  - 15/01/2024, 14:48:23   ERROR [ExceptionHandler] Nest can't resolve dependencies of the AuthService (JwtService, ?). Please make sure that the argument dependency at index [1] is available in the AuthModule context.

Potential solutions:
- Is AuthModule a valid NestJS module?
- If dependency is a provider, is it part of the current AuthModule?
- If dependency is exported from a separate @Module, is that module imported within AuthModule?
  @Module({
    imports: [ /* the Module containing dependency */ ]
  })

项目核心代码 #

app.module #

@Module({
  imports: [
    ConfigModule.forRoot({
      isGlobal: true,
      load: [typeormConfig],
    }),
    TypeOrmModule.forRootAsync({
      inject: [ConfigService],
      useFactory: async (configService: ConfigService) =>
        configService.get('typeorm'),
    }),
    AuthModule,
    UserModule,
    FormModule,
  ],
  controllers: [AppController],
  providers: [],
})
export class AppModule {}

auth.module #

@Module({
  imports: [
    ConfigModule.forRoot(),
    JwtModule.register({
      secret: process.env.SECRET_JWT,
    }),
    UserModule,
  ],
  providers: [AuthService],
  controllers: [AuthController],
})
export class AuthModule {}

auth.service #

@Injectable()
export class AuthService extends AbstractService {
  constructor(
    private readonly JWTService: JwtService,
    private readonly userService: UserService,
  ) {
    super(AuthService.name);
  }

    ...
}

user.module #

@Module({
  imports: [TypeOrmModule.forFeature([UserEntity])],
  providers: [UserService],
  exports: [UserService],
  controllers: [UserController],
})
export class UserModule {}

user.service #

@Injectable()
export class UserService extends AbstractService {
  constructor(
    @InjectRepository(UserEntity)
    private usersRepository: Repository<UserEntity>,
  ) {
    super(UserService.name);
  }

  ...
}

auth.guard #

@Injectable()
export class AuthGuard extends AbstractGuard {
  constructor(private readonly authService: AuthService) {
    super(AuthGuard.name);
  }

   ...
}

form.module（使用Guard的模块） #

@Module({
  imports: [TypeOrmModule.forFeature([FormEntity, UserEntity]), QuestionModule],
  exports: [FormService],
  providers: [FormService],
  controllers: [FormController],
})
export class FormModule {}

abstract.service #

@Injectable()
export class AbstractService {
  protected readonly logger: Logger;

  constructor(context: string) {
    this.logger = new Logger(context);
  }
}

排查原因与解决方案 #

核心原因 #

AppModule中模块导入顺序错误：AuthModule在UserModule之前加载，而AuthModule依赖UserModule导出的UserService，导致AuthModule初始化时UserModule尚未完成初始化，无法解析UserService依赖。

具体修复步骤 #

1. 调整AppModule的模块导入顺序
   将UserModule移至AuthModule之前，确保依赖模块先完成初始化：

   @Module({
     imports: [
       ConfigModule.forRoot({
         isGlobal: true,
         load: [typeormConfig],
       }),
       TypeOrmModule.forRootAsync({
         inject: [ConfigService],
         useFactory: async (configService: ConfigService) =>
           configService.get('typeorm'),
       }),
       UserModule, // 先导入UserModule
       AuthModule, // 再导入依赖UserModule的AuthModule
       FormModule,
     ],
     controllers: [AppController],
     providers: [],
   })
   export class AppModule {}
   

2. 移除AuthModule中重复的ConfigModule导入
   AppModule已将ConfigModule设为全局模块，无需在AuthModule中重复调用ConfigModule.forRoot()，避免配置冲突：

   @Module({
     imports: [
       // 移除这行：ConfigModule.forRoot(),
       JwtModule.register({
         secret: process.env.SECRET_JWT,
       }),
       UserModule,
     ],
     providers: [AuthService],
     controllers: [AuthController],
   })
   export class AuthModule {}
   

3. 优化JwtModule配置（可选但推荐）
   改用异步注册方式，通过全局ConfigService获取JWT密钥，避免环境变量加载时机问题：

   @Module({
     imports: [
       JwtModule.registerAsync({
         inject: [ConfigService],
         useFactory: (configService: ConfigService) => ({
           secret: configService.get<string>('SECRET_JWT'),
         }),
       }),
       UserModule,
     ],
     providers: [AuthService],
     controllers: [AuthController],
   })
   export class AuthModule {}
   

4. 验证UserService的导入（必查）
   确保AuthService文件顶部正确导入了UserService类，否则TypeScript无法识别类型，导致Nest无法解析依赖：

   // 在auth.service.ts顶部添加
   import { UserService } from '../user/user.service';
   

补充说明 #

如果项目中存在UserService与AuthService的循环依赖（比如UserService也依赖AuthService），则需要使用forwardRef处理：

• 在AuthModule中导入UserModule时使用forwardRef(() => UserModule)
• 在UserModule中导入AuthModule时同样使用forwardRef(() => AuthModule)
• 在构造函数中注入时配合@Inject(forwardRef(() => ServiceClass))装饰器

但根据当前提供的代码，不存在循环依赖，调整导入顺序即可解决问题。

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