globalSetup.ts script ignores tsconfig.json

Issue

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

Actual behavior

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

Minimal repo

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

[Eoksni]

Adding require("tsconfig-paths/register"); at the top of globalSetup seems to fix it. This works for me globalSetup.ts:

require("tsconfig-paths/register");

import logger from "src/logger";
...

export = async function(): Promise<void> {
  logger.log('Jest Global Setup');
};

[ahnpnl]

Hmm look like moduleNameMapper only works in test files and doesn’t seem to work with globalSetup.