NestJS无法解析AuthController的MeService依赖，求解决方案

问题描述 #

运行NestJS认证功能时触发以下错误：

Error: Nest can't resolve dependencies of the AuthController (?, LoginService, LogoutService). Please make sure that the argument MeService at index [0] is available in the AuthModule context.

已尝试移除forwardRef函数，但错误仍未解决。

相关代码片段 #

AuthController.ts #

@Controller('auth')
export class AuthController {
    constructor(
        private readonly meService: MeService,
        private readonly loginService: LoginService,
        private readonly logoutService: LogoutService
    ) {}

AuthModule.ts #

@Module({
    imports: [forwardRef(() => UsersModule)],
    providers: [MeService, LoginService, LogoutService],
    controllers: [AuthController]
})
export class AuthModule {}

UsersModule.ts #

@Module({
    imports: [RolesModule, TypeOrmModule.forFeature([User])],
    providers: [
        UserRepository,
        ShowService,
        IndexService,
        CreateService,
        UpdateService,
        DeleteService
    ],
    controllers: [UsersController],
    exports: [UserRepository]
})
export class UsersModule {}

MeService.ts #

@Injectable()
export class MeService {
    constructor(
        @Inject(forwardRef(() => UserRepository))
        private userRepository: UserRepository
    ) {}

    async handle(id: string): Promise<User> {
        if (!id) {
            throw new UnauthorizedException(en.unauthorized);
        }

        return this.userRepository.findOne({
            where: { id },
            relations: {
                createdBy: true,
                role: true
            },
            withDeleted: true
        });
    }
}

UserRepository.ts #

@Injectable()
export class UserRepository extends AbstractRepository<User> {
    constructor(
        @InjectRepository(User)
        protected readonly repository: Repository<User>
    ) {
        super();
    }

    async findByEmail(email: string, options: FindOneOptions<User> = {}) {
        const finalOptions = deepMerge(options, { where: { email } });

        return this.repository.findOne(finalOptions);
    }
}

AbstractRepository.ts #

@Injectable()
export abstract class AbstractRepository<T extends { id: string }> {
    protected abstract readonly repository: Repository<T>;

    findAll(options: FindManyOptions<T> = {}): Promise<T[]> {
        return this.repository.find(options);
    }
}

解决方案 #

1. 修复循环依赖的双向配置 #

如果UsersModule同样依赖AuthModule，必须在UsersModule的imports中也添加forwardRef(() => AuthModule)，单向的forwardRef无法解决跨模块循环依赖问题。

2. 简化MeService的注入方式 #

MeService中对UserRepository的@Inject(forwardRef(...))是冗余操作，因为UserRepository已通过UsersModule导出，且AuthModule已导入UsersModule，直接注入即可：

// 修改后的MeService构造函数
constructor(
    private readonly userRepository: UserRepository
) {}

3. 清理项目缓存并重启 #

NestJS的依赖注入缓存可能导致异常，执行以下操作：

• 删除项目根目录下的dist文件夹；
• 停止开发服务器后重新启动；
• 执行npm run build重新构建项目。

4. 排查重复服务声明 #

确保MeService仅在AuthModule的providers数组中声明，未在其他模块重复提供，避免Nest无法确定使用哪个实例。

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