globalSetup.ts script ignores tsconfig.json

🐛 Bug Report

When tsconfig.json has defined compilerOptions.baseUrl, absolute paths can be used within test files for importing items. However, same TS code placed in globalSetup script handles only relative paths. Looks like tsconfig is simply ignored while running globalSetup.

To Reproduce

Steps to reproduce the behavior:

1. checkout https://github.com/4ekki/jest-globalSetup-import-bug. Note that first line of scripts/globalSetup.ts file is : import { sleep } from "../tests/src"
2. run yarn test smoke
3. change first line of scripts/globalSetup.ts file to: import { sleep } from "src"
4. run yarn test smoke

As a result: On 2, globalSetup script is run successfully with relative path. Also, import with absolute path is successfully handled in test file.

On 4, globalSetup script fails to import sleep from src, using absolute path:

Expected behavior

On 4, absolute paths in globalSetup.ts are resolved using compilerOptions.baseUrl property from tsconfig.json

Link to repl or repo (highly encouraged)

https://github.com/4ekki/jest-globalSetup-import-bug

Run npx envinfo --preset jest

$ npx envinfo --preset jest
npx: installed 1 in 1.962s

  System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  Binaries:
    Node: 10.5.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.7.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.1.0 - C:\Program Files\nodejs\npm.CMD

[SimenB]

Not yet. Note that this is very unlikely to be a bug in jest as we do not support tsconfig at all out of the box (we use babel), most likely your issue is with ts-jest. However, I’d like to verify (although I haven’t found the time yet)

[4ekki]

I’ve duplicated this to ts-jest tracker as well - https://github.com/kulshekhar/ts-jest/issues/1107