Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

229
Views
Run jest tests on compiled JS

Recently(constant) i got some problems with jest/ts-jest setup. Memory leaks, low performance. I have got an idea to first compile typescript to javascript using tsc, and then run jest agains these js files. But jest is still trying to resolve require() paths into .ts files instead of .js files. Does anyone had a similar problem?

jest config

  "jest": {
    "moduleFileExtensions": [
      "js",
      "json"
    ],
    "rootDir": "dist",
    "testRegex": ".spec.js$",
    "testEnvironment": "node"
  },

jest version : 27.0.6

run script

node --expose-gc ./node_modules/.bin/jest --setupFiles dotenv/config --runInBand --detectOpenHandles --forceExit --logHeapUsage

sample error

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    SyntaxError: /Users/jakub/Projects/project/src/config/orm.config.ts: Unexpected reserved word 'interface'. (2:0)

      1 | import { TypeOrmModuleOptions } from '@nestjs/typeorm';
    > 2 | interface SeedingOptions {
        | ^
      3 |   factories: string[];
      4 |   seeds: string[];
      5 | }

it should use dist/config/orm.config.js instead of src/config/orm.config.ts

compiled import line

var __importDefault = (this && this.__importDefault) || function (mod) {
    return (mod && mod.__esModule) ? mod : { "default": mod };
};
Object.defineProperty(exports, "__esModule", { value: true });
const orm_config_1 = __importDefault(require("./../config/orm.config"));
about 4 years ago · Juan Pablo Isaza
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!