Cannot find module '@tsed/components-scan' error when using supertest #2197

LefanTan · 2022-12-25T04:15:29Z

LefanTan
Dec 25, 2022

Hi folks,

I'm running into issues when using supertest, receiving this error when running it.

    Cannot find module '@tsed/components-scan' from 'node_modules/@tsed/common/lib/cjs/services/PlatformTest.js'

      at Resolver._throwModNotFoundError (node_modules/jest-resolve/build/resolver.js:425:11)
      at node_modules/@tsed/common/src/services/PlatformTest.ts:59:35
      at Object.before (node_modules/@tsed/common/src/services/PlatformTest.ts:59:35)

Here's my jest config

// For a detailed explanation regarding each configuration property, visit:
// https://jestjs.io/docs/en/configuration.html

const { pathsToModuleNameMapper } = require("ts-jest");
const { compilerOptions } = require("./tsconfig");

/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
  moduleNameMapper: {
    ...pathsToModuleNameMapper(compilerOptions.paths, { prefix: "<rootDir>/" }),
  },

  // Automatically clear mock calls and instances between every test
  clearMocks: true,

  // Indicates whether the coverage information should be collected while executing the test
  collectCoverage: true,

  // An array of glob patterns indicating a set of files for which coverage information should be collected
  // collectCoverageFrom: undefined,

  // The directory where Jest should output its coverage files
  coverageDirectory: "coverage",

  // An array of regexp pattern strings used to skip coverage collection
  coveragePathIgnorePatterns: ["index.ts", "/node_modules/", "prisma"],

  // An object that configures minimum threshold enforcement for coverage results
  coverageThreshold: {
    global: {
      branches: 70,
      functions: 70,
      lines: 70,
      statements: 70,
    },
  },

  // An array of file extensions your modules use
  moduleFileExtensions: ["js", "json", "jsx", "ts", "tsx", "node"],

  // The test environment that will be used for testing
  testEnvironment: "node",

  // The glob patterns Jest uses to detect test files
  testMatch: [
    "**/src/**/__tests__/**/*.[jt]s?(x)",
    "**/src/**/?(*.)+(spec|test).[tj]s?(x)",
    "**/tests/**/?(*.)+(spec|test).[tj]s?(x)",
  ],
  // A map from regular expressions to paths to transformers
  transform: {
    "\\.(ts)$": "ts-jest",
  },
};

and test file

import { PlatformTest } from "@tsed/common";
import SuperTest from "supertest";

import { UserModel } from "@generated";
import { Server } from "@src/Server";

describe("UserController", () => {
  let request: SuperTest.SuperTest<SuperTest.Test>;

  beforeAll(PlatformTest.create);
  beforeAll(PlatformTest.bootstrap(Server));
  beforeAll(() => {
    request = SuperTest(PlatformTest.callback());
  });
  afterAll(PlatformTest.reset);

  describe("POST /create", () => {
    it("should return a new user", async () => {
      const newUser: UserModel = {
        id: "123",
        name: "jacob",
        email: "[email protected]",
        recording: [],
        createdAt: new Date(),
        updatedAt: new Date(),
        profilePhotoUrl: null,
      };

      const response = await request.post("/create").send({ user: newUser });

      expect(response.status).toBe(200);
      expect(response.body).toEqual(newUser);
    });
  });
});

My codebase is using path aliases through services and controllers, and with the help of the tsc-alias to make it work in production build. This all worked fine except for running tests, curious if there's anything wrong with my configuration? Thanks and much appreciated