CircleCI Jest error with ts-jest@25.3.0

[thinkh]

• Release number or git hash: create a new branch on tdp_core
• Web browser version and OS: independent
• Environment (local or deployed): independent

Observed behavior

1. ✔ CircleCI build 1559: lineupjs4 branch from 30.03.2020
2. ❌ CircleCI build 1561: thinkh/331_string-filter-compatibility branch from 30.03.2020
   • first occurence of Jest error
3. ❌ CircleCI build 1570: thinkh/347_fix-overview-column branch from 01.04.2020
   • fixes LineUp v4 compile errors in OverviewColumn #347 and fails because of Jest error
4. ❌ CircleCI build 1581: rebuild of lineupjs4 branch from 01.04.2020
   • same commit as build 1559
   • fails because of LineUp v4 compile errors in OverviewColumn #347 and not because of Jest error

> tdp_core@9.1.1-SNAPSHOT test:web /home/circleci/phovea
> test ! $(find tests -name "*.ts") || jest

sh: 1: test: tests/lineup/internal/cmds.test.ts: unexpected operator
 PASS  tests/cached.test.ts
 FAIL  tests/lineup/internal/cmds.test.ts
  ● Test suite failed to run

    TypeError: Unable to require `.d.ts` file for file: index.ts.
    This is usually the result of a faulty configuration or import. Make sure there is a `.js`, `.json` or another executable extension available alongside `index.ts`.

      at compileFn (node_modules/ts-jest/dist/compiler/language-service.js:74:23)
      at Object.compile (node_modules/ts-jest/dist/compiler/instance.js:81:25)
      at TsJestTransformer.process (node_modules/ts-jest/dist/ts-jest-transformer.js:96:41)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:446:35)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:525:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:563:25)

 FAIL  tests/select3.test.ts
  ● Test suite failed to run

    TypeError: Unable to require `.d.ts` file for file: index.ts.
    This is usually the result of a faulty configuration or import. Make sure there is a `.js`, `.json` or another executable extension available alongside `index.ts`.

      at compileFn (node_modules/ts-jest/dist/compiler/language-service.js:74:23)
      at Object.compile (node_modules/ts-jest/dist/compiler/instance.js:81:25)
      at TsJestTransformer.process (node_modules/ts-jest/dist/ts-jest-transformer.js:96:41)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:446:35)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:525:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:563:25)

Test Suites: 2 failed, 1 passed, 3 total
Tests:       2 passed, 2 total
Snapshots:   0 total
Time:        4.229s
Ran all test suites.

Expected behavior

The test should run without errors.

[thinkh]

After a lot of test-and-error CircleCI builds I found the error between the last successful build #1559 and #1561 with the following two diff in the dependency logs:

  ├─┬ jest@25.1.0
- │ ├── @jest/core@25.2.3
+ │ ├── @jest/core@25.2.4
  │ ├── import-local@3.0.2
- │ └── jest-cli@25.2.3
+ │ └── jest-cli@25.2.4

- ├─┬ ts-jest@25.2.1
+ ├─┬ ts-jest@25.3.0
  │ ├── bs-logger@0.2.6
  │ ├── buffer-from@1.1.1
  │ ├── fast-json-stable-stringify@2.1.0
  │ ├── json5@2.1.2
  │ ├── lodash.memoize@4.1.2
  │ ├── make-error@1.3.6
- │ ├── mkdirp@0.5.4 deduped
+ │ ├── mkdirp@1.0.3
  │ ├── resolve@1.15.1 deduped
- │ ├── semver@5.7.1
- │ └── yargs-parser@16.0.1
+ │ ├── semver@6.3.0
+ │ └── yargs-parser@18.1.2

Since jest itself has not changed, the error must be caused by ts-jest. Reverting the ts-jest version to the last version 25.2.1 fixed the CircleCI problem.

The ts-jest changelog v25.3.0 states a breaking change:

25.3.0 (2020-03-30)

Bug Fixes

• add jest-config to dependencies list (6d9e0d8)
• always do type check for all files provided to ts-jest transformer (#1450) (107e062)
• docs: correct changelog, correct version in package.json (#1406) (542e181)

Chores

• config: improve diagnostics message (#1444) (96cd9b3)

Features

• compiler: expose internal ts Program via ConfigSet TsCompiler (#1433) (7153246)
• config: add incremental option (#1418) (5a69bce)

BREAKING CHANGES

• config: This will affect to any snapshots or assertion against diagnostics messages

Furthermore, we cache the npm dependencies on CircleCI for a specific branch and only update them when the package.json is changed OR a new branch is pushed.

[thinkh]

Explanation what has happened:

• build 1559 of lineupjs4 is successful, because ts-jest was not released at that time
• ts-jest@25.3.0 was released
• build 1561 of thinkh/331_string-filter-compatibility fails
  • reason: new branch = install new npm dependencies with ts-jest
• build 1570 of thinkh/347_fix-overview-column fails
  • reason: new branch = install new npm dependencies with ts-jest

I expect other branches (also from develop branch) to fail, because they will install the new ts-jest version.

The fix would be switch to the ~ version for ts-jest:

- "ts-jest": "^25.2.1",
+ "ts-jest": "~25.2.1",

@anita-steiner and @dvvanessastoiber would that work that fix for you?