NestJS依赖注入错误：UserService无法解析UserModel依赖

问题场景 #

构建带身份认证的NestJS API，集成MongoDB存储食谱，新增用户邮件确认功能时触发依赖注入错误，提示UserModel无法在EmailModule上下文中解析。

报错信息 #

Error: Nest can't resolve dependencies of the UserService (?). Please make sure that the argument UserModel at index [0] is available in the EmailModule context.

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

    at Injector.lookupComponentInParentModules (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\injector.js:241:19)
    at Injector.resolveComponentInstance (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\injector.js:194:33)
    at resolveParam (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\injector.js:116:38)
    at async Promise.all (index 0)
    at Injector.resolveConstructorParams (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\injector.js:131:27)
    at Injector.loadInstance (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\injector.js:57:13)
    at Injector.loadProvider (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\injector.js:84:9)
    at async Promise.all (index 4)
    at InstanceLoader.createInstancesOfProviders (C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\instance-loader.js:47:9)
    at C:\Users\Jonathan\Documents\Repos\pantry-api\node_modules\@nestjs\core\injector\instance-loader.js:32:13

问题根源 #

1. 模块服务共享机制错误：UserModule未导出UserService，导致其他模块无法通过导入UserModule获取到合法的UserService实例。
2. 重复声明服务：EmailModule和AuthModule均直接在providers中声明了UserService，Nest会尝试在当前模块上下文创建新实例，但EmailModule未导入UserModel的依赖，导致注入失败。
3. JwtService依赖未正确引入：EmailModule直接声明JwtService，未通过JwtModule导入，导致依赖缺失。

修复步骤 #

1. 修改UserModule，导出UserService #

让UserModule导出自身提供的UserService，确保其他模块导入UserModule后能直接使用该服务：

import { Module } from "@nestjs/common";
import { MongooseModule } from "@nestjs/mongoose";
import { User, UserSchema } from "./schemas/user.schema";
import { UserController } from "./user.controller";
import { UserService } from "./user.service";

@Module({
  imports: [MongooseModule.forFeature([{ name: User.name, schema: UserSchema }])],
  controllers: [UserController],
  providers: [UserService],
  exports: [UserService] // 新增导出配置
})
export class UserModule {}

2. 重构EmailModule，清理重复声明 #

移除重复的UserService和JwtService声明，通过导入模块获取依赖，并添加自身服务的声明与导出：

import { Module } from "@nestjs/common";
import { ConfigModule } from "@nestjs/config";
import { JwtModule } from "@nestjs/jwt";
import { UserModule } from "src/user/user.module";
import EmailService from "./email.service";
import { EmailConfirmationService } from "./emailConfirmation.service";

@Module({
  imports: [
    ConfigModule,
    UserModule,
    JwtModule.registerAsync({
      imports: [ConfigModule],
      useFactory: (configService) => ({
        secret: configService.get("JWT_VERIFICATION_TOKEN_SECRET"),
        signOptions: { expiresIn: `${configService.get("JWT_VERIFICATION_TOKEN_EXPIRATION_TIME")}s` }
      }),
      inject: [ConfigModule]
    })
  ],
  controllers: [],
  providers: [EmailService, EmailConfirmationService],
  exports: [EmailConfirmationService] // 导出供AuthModule使用
})
export class EmailModule {}

3. 清理AuthModule的重复声明 #

移除重复的UserService、ConfigService和EmailConfirmationService声明，通过导入对应模块获取依赖：

import { Module } from "@nestjs/common";
import { ConfigModule, ConfigService } from "@nestjs/config";
import { JwtModule } from "@nestjs/jwt";
import { MongooseModule } from "@nestjs/mongoose";
import { PassportModule } from "@nestjs/passport";
import { EmailModule } from "src/email/email.module";
import { User, UserSchema } from "src/user/schemas/user.schema";
import { UserModule } from "src/user/user.module";
import { AuthController } from "./auth.controller";
import { AuthService } from "./auth.service";
import { JwtStrategy } from "./jwt.strategy";
import { LocalStrategy } from "./local.auth";

@Module({
  imports: [
    UserModule,
    EmailModule,
    PassportModule,
    ConfigModule,
    JwtModule.registerAsync({
      imports: [ConfigModule],
      useFactory: (configService: ConfigService) => ({
        secret: configService.get("JWT_SECRET"),
        signOptions: { expiresIn: "10m" }
      }),
      inject: [ConfigService]
    }),
    MongooseModule.forFeature([{ name: User.name, schema: UserSchema }]),
  ],
  providers: [AuthService, JwtStrategy, LocalStrategy],
  controllers: [AuthController],
})
export class AuthModule {}

4. 修复UserService的逻辑错误 #

markEmailAsConfirmed方法中，updateOne参数应为用户ID而非邮箱，修正如下：

async markEmailAsConfirmed(email: string) {
  const user = await this.findOne(email);
  return this.updateOne(user._id.toString(), {...user, status: AccountStatus.Confirmed})
}

总结 #

核心问题是未遵循NestJS模块间服务共享的导出/导入规则，通过让服务提供模块导出服务、使用方模块导入对应模块，即可解决依赖上下文不匹配的问题，同时避免重复声明服务导致的资源浪费与注入错误。

内容的提问来源于stack exchange，提问作者Jonathan Van Dyck