NodeJS - Running tests with Jest: getting an error with TypeScript config file

Question

I'm trying to run some tests with Jest but I keep getting an error. It's something to do with a TypeScript config file, I already searched but didn't find much. I'm using NodeJS, TypeORM with TypeScript.

I'm getting this error when running yarn test:

Error: Jest: Failed to parse the TypeScript config file

C:\Users\demis\Documents\Projects\Personal\nlw_node\jest.config.ts TypeError: registerer.enabled is not a function*** at readConfigFileAndSetRootDir (C:\Users\demis\Documents\Projects\Personal\nlw_node\node_modules\jest-config\build\readConfigFileAndSetRootDir.js:150:13) at readConfig (C:\Users\demis\Documents\Projects\Personal\nlw_node\node_modules\jest-config\build\index.js:217:18) at readConfigs (C:\Users\demis\Documents\Projects\Personal\nlw_node\node_modules\jest-config\build\index.js:406:26) at runCLI (C:\Users\demis\Documents\Projects\Personal\nlw_node\node_modules@jest\core\build\cli\index.js:230:59) at Object.run (C:\Users\demis\Documents\Projects\Personal\nlw_node\node_modules\jest-cli\build\cli\index.js:163:37)

First.test.ts:

describe("First", () => {
  it("should", () => {
    expect(2 + 2).toBe(4);
  });
});

jest.config.ts:

export default {
  bail: true,
  clearMocks: true,
  coverageProvider: "v8",
  preset: "ts-jest",
  testEnvironment: "node",
  testMatch: ["**/tests/*.test.ts"]
};

tsconfig.json:

{
   "compilerOptions": {
      "lib": [
         "es5",
         "es6"
      ],
      "target": "es5",
      "module": "commonjs",
      "moduleResolution": "node",
      "outDir": "./build",
      "emitDecoratorMetadata": true,
      "experimentalDecorators": true,
      "sourceMap": true
   }
}

package.json:

{
  "name": "nlw_node",
  "version": "0.0.1",
  "description": "Awesome project developed with TypeORM.",
  "devDependencies": {
    "@types/express": "^4.17.11",
    "@types/jest": "^26.0.20",
    "@types/node": "^8.0.29",
    "@types/uuid": "^8.3.0",
    "jest": "^26.6.3",
    "nodemon": "^2.0.7",
    "ts-jest": "^26.5.3",
    "ts-node": "3.3.0",
    "typescript": "^4.2.3"
  },
  "dependencies": {
    "body-parser": "^1.18.1",
    "express": "^4.15.4",
    "mysql": "^2.14.1",
    "reflect-metadata": "^0.1.10",
    "typeorm": "0.2.31",
    "uuid": "^8.3.2"
  },
  "scripts": {
    "start": "nodemon src/index.ts",
    "typeorm": "ts-node node_modules/typeorm/cli.js",
    "test": "jest"
  }
}

ormconfig.ts:

{
  "type": "mysql",
  "host": "localhost",
  "port": 3306,
  "username": "root",
  "password": "root",
  "database": "nlw_node",
  "synchronize": true,
  "logging": false,
  "entities": ["src/api/models/**.ts"],
  "migrations": ["src/database/migrations/**.ts"],
 
  "cli": {
    "entitiesDir": "src/entity",
    "migrationsDir": "./src/database/migrations",
    "subscribersDir": "src/subscriber"
  }
}

The problem is you have type="module" in your package.json (which is required by sveltekit in my case). I have no idea how to fix though. — chovy
– chovy, Commented May 4, 2022 at 7:23

0Valt · Accepted Answer · 2023-05-23 07:58:14Z

11

Remove the ts-node package and install ts-node-dev instead.

edited May 23, 2023 at 7:58

0Valt

10.5k9 gold badges41 silver badges66 bronze badges

answered Aug 31, 2021 at 19:40

Jonathan Bertoldi

1191 silver badge3 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Itamar K. Over a year ago

Upgrading ts-node version to latest (^10.9.1 in my case) worked for me.

Devorein · Accepted Answer · 2023-08-09 11:25:30Z

10

I had the silliest of issues. There was a comma at the end of my tsconfig file like the following:-

{
  ...
  "ts-node": {
    "compilerOptions": {
      "jsx": "react-jsx",
      "module": "commonjs",
      "jsxImportSource": "",
      "paths": {
        "~/*": [
          "./src/*"
        ]
      }
    },
    "require": [
      "tsconfig-paths/register"
    ],
    "transpileOnly": true
  }, // <----- This was the offending comma
}

Removing this comma fixed the issue for me.

edited Aug 9, 2023 at 11:25

answered Jul 24, 2023 at 12:45

Devorein

1,3792 gold badges19 silver badges26 bronze badges

3 Comments

Ken Boreham Over a year ago

This led me to the correct solution for my case. I had commented out a compilerOption which normally isn't an issue and went unnoticed until I ran tests. In my jest.config I import tsconfig.json for paths. At that point tsconfig needs to be properly formed JSON.

Elizabeth Oyekunle Over a year ago

I would have been stuck on this issue for hours if I didn't see this answer. This worked for me, I had an extra comma at the end of my paths. Thank you so much

Samuel Goldenbaum Jan 21 at 19:36

check you also have no comments in the tsconfig.json

ggorlen · Accepted Answer · 2023-01-19 23:35:37Z

4

I had exactly the same error this am, trying to run tests in jest with Angular and Typescript.

My problem was solved by re-installing jest:

npm install --save-dev jest

This then showed an underlying configuration issue with my set up - but at least I don't see the failed error.

edited Jan 19, 2023 at 23:35

ggorlen

59.3k8 gold badges119 silver badges173 bronze badges

answered Mar 16, 2021 at 9:51

PaulGrant

4244 silver badges9 bronze badges

Comments

Levente Orbán · Accepted Answer · 2023-05-16 14:54:04Z

2

Installing ts-jest should solve this problem if you have ts-node installed.

answered May 16, 2023 at 14:54

Levente Orbán

8513 bronze badges

Comments

Rodrigo João Bertotti · Accepted Answer · 2022-02-01 12:25:03Z

1

Check if the babel.config.js file is in the root / folder of the project, if is not the problem follow these instructions

edited Feb 1, 2022 at 12:25

answered Aug 20, 2021 at 18:46

Rodrigo João Bertotti

5,5913 gold badges28 silver badges44 bronze badges

Comments

Matt Oestreich · Accepted Answer · 2025-02-06 15:55:42Z

1

Wanting to leave this here just in case it helps someone.

TLDR; run your IDE's "format this file" functionality on your tsconfig.json.

This is the error I was getting:

SyntaxError: /Users/foo/bar/baz/project/tsconfig.json: Expected double-quoted property name in JSON at position 495 (line 20 column 5)

I couldn't find the offending (assumed) single quote, or, well, anything wrong with it all. I wasted so much time on this lol..

The fix was to literally just right click inside my tsconfig.json file and format it (I'm using VSCode FYI).

answered Feb 6 at 15:55

Matt Oestreich

8,6163 gold badges19 silver badges46 bronze badges

Comments

Ercio Alendre · Accepted Answer · 2022-07-08 16:59:23Z

I added exclude and include on my tsconfig.json file and it worked.

{
  "compilerOptions": {
    "target": "esnext",
    "module": "commonjs",
    "rootDir": "./",
    "baseUrl": "./src",
    "outDir": "./dist",
    "allowJs": true,
    "noEmit": false,
    "noEmitOnError": true,
    "noUnusedLocals": true,
    "strict": true,
    "moduleResolution": "node",
    "sourceMap": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "forceConsistentCasingInFileNames": true,
    "removeComments": true,
    "skipLibCheck": true,
    "typeRoots": [
      "@types",
      "./node_modules/@types"
    ]
  },
  "exclude": [
    "node_modules",
    "dist"
  ],
  "include": [
    "src/**/*",
    "src/__tests__",
    "jest.config.js"
  ]
}

ggorlen · Accepted Answer · 2023-01-19 23:35:54Z

0

I had the same problem, but the tests were running once.

It turned out I needed to delete node_modules and yarn.lock and reinstall everything again.

edited Jan 19, 2023 at 23:35

ggorlen

59.3k8 gold badges119 silver badges173 bronze badges

answered Jan 7, 2023 at 12:50

Marian Klühspies

18k20 gold badges112 silver badges167 bronze badges

Collectives™ on Stack Overflow

NodeJS - Running tests with Jest: getting an error with TypeScript config file

8 Answers 8

1 Comment

3 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

8 Answers 8

1 Comment

3 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related