Error: Command failed: pnpm run --filter ./api coverage The CJS build of Vite's Node API is deprecated. See https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated for more details. stderr | src/@common/users/user/profile/profile-picture/profile-picture.service.spec.ts > ProfilePictureService > should be defined warn(prisma-client) This is the 10th instance of Prisma Client being started. Make sure this is intentional. ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 2 ⎯⎯⎯⎯⎯⎯⎯ FAIL src/message/message.controller.spec.ts > MessageController > should be defined Error: Nest can't resolve dependencies of the MessageController (?). Please make sure that the argument PrismaService at index [0] is available in the RootTestModule context. Potential solutions: - Is RootTestModule a valid NestJS module? - If PrismaService is a provider, is it part of the current RootTestModule? - If PrismaService is exported from a separate @module, is that module imported within RootTestModule? @module({ imports: [ /* the Module containing PrismaService */ ] }) ❯ TestingInjector.lookupComponentInParentModules ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/injector.js:254:19 ❯ TestingInjector.resolveComponentInstance ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/injector.js:207:33 ❯ TestingInjector.resolveComponentInstance ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected]_@[email protected]/node_modules/@nestjs/testing/testing-injector.js:19:45 ❯ resolveParam ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/injector.js:128:38 ❯ TestingInjector.resolveConstructorParams ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/injector.js:143:27 ❯ TestingInjector.loadInstance ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/injector.js:70:13 ❯ TestingInjector.loadController ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/injector.js:88:9 ❯ ../node_modules/.pnpm/@nestjs[email protected]_@[email protected]_@[email protected][email protected][email protected]/node_modules/@nestjs/core/injector/instance-loader.js:68:13 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { context: { index: +0, dependencies: [ 'Function<PrismaService>' ], name: 'Function<PrismaService>' }, metadata: { id: '9b95b98673b57aa102805' }, moduleRef: { id: 'e3874013c39b95b98673b' }, what: 'Function<what>' } ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/2]⎯ FAIL src/@common/users/admin/admin.controller.spec.ts > AdminController > should be defined Error: Nest can't resolve dependencies of the AdminController (?, AuthService, PrismaService, PresenceService). Please make sure that the argument AdminService at index [0] is available in the RootTestModule context. Potential solutions: - Is RootTestModule a valid NestJS module? - If AdminService is a provider, is it part of the current RootTestModule? - If AdminService is exported from a separate @modul