Error: Nest can't resolve dependencies

[ebadmail]

Describe the bug

FAIL  src/content/content.controller.spec.ts > ContentController > should be defined
Error: Nest can't resolve dependencies of the ContentService (?, PrismaServiceCLSS, ReferenceSystemService, ContactService, LookUpService). Please make sure that the argument PrismaServiceMM at index [0] is available in the RootTestModule context.

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

Reproduction

Hello everyone! I'm encountering a problem while running vitest on NestJS, specifically when dealing with composite providers. There's an instance we declared as provided, which also requires a provider to be set in the code declaration. Surprisingly, I'm not encountering any errors when using Jest. In the example below ContentService requires PrismaServiceMM.

describe('ContentController', () => {
  let controller: ContentController;

  beforeEach(async () => {
    const module: TestingModule = await Test.createTestingModule({
      controllers: [ContentController],
      providers: [
        ContentService,
        PrismaServiceMM
      ],
    }).compile();

    controller = module.get<ContentController>(ContentController);
  });

  it('should be defined', () => {
    expect(controller).toBeDefined();
  });

export class ContentController {
  constructor(private readonly contentService: ContentService) {}
  ...
 }

export class ContentService {
  constructor(
    private prismaMM: PrismaServiceMM,
    private contactService: ContactService,
    private lookUpService: LookUpService,
  ) {}
  ...
}

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
    Memory: 3.66 GB / 15.72 GB
  Binaries:
    Node: 20.8.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.4.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (123.0.2420.97)
    Internet Explorer: 11.0.19041.3636
  npmPackages:
    @vitest/coverage-v8: ^1.2.2 => 1.2.2
    @vitest/ui: ^1.2.2 => 1.2.2
    vitest: ^1.2.2 => 1.2.2

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[hi-ogawa]

Can you provide a minimal runnable reproduction? You can maybe start with the simple example in https://github.com/vitest-dev/vitest/tree/main/examples

[github-actions[bot]]

Hello @ebadmail. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.

[ebadmail]

@hi-ogawa Thank you for your reply. As requested here is a minimal runnable reproduction.

https://stackblitz.com/edit/vitest-dev-vitest-dw1ndp

[hi-ogawa]

Hmm, this feels like simply a nest js usage error though I'm not familiar with it.

There are a few things I felt shaky from my non-nestjs user instinct:

• missing providers

// nestjs.test.ts
    const module: TestingModule = await Test.createTestingModule({
      controllers: [CatsController],
-      providers: [CatsService],
+      providers: [CatsService, DbService],
    }).compile();

• type import for dependency injection

// cats.controller.ts
- import type { Cat, CatsService } from './cats.service';
+ import { Cat, CatsService } from './cats.service';

After fixing these two, it looks working to me:
https://stackblitz.com/edit/vitest-dev-vitest-vrwwj2?file=src%2Fcats.controller.ts

I don't know why the same thing would work on Jest.