[Bug]: jest ts-node ignores provided tsconfig.json

[CyberCookie]

Version

28.0.5

Steps to reproduce

Create valid jest.config.ts file wit the next content:

import { InitialOptionsTsJest } from 'ts-jest'
import path from 'path'

console.log(import.meta)

const jestOptions: InitialOptionsTsJest = {
    preset: 'ts-jest/presets/default-esm',
    rootDir: './some_root',
    testMatch: [ '**/*.test.ts' ],
    extensionsToTreatAsEsm: ['.ts'],
    moduleNameMapper: {
        '^(\\.{1,2}/.*)\\.js$': '$1'
    },
    globals: {
        'ts-jest': {
            useESM: true,
            tsconfig: path.join(process.cwd(), 'tsconfig.json')
        }
    }
}

export default jestOptions

Note console.log(import.meta)

Create valid tsconfig.json file:

{
    "compilerOptions": {
	"target": "esnext",
        "module": "esnext",
	"moduleResolution": "node",
        "allowJs": true,
	"esModuleInterop": true,
        "strict": true,
	"skipLibCheck": true,
        "declaration": true,
        "allowSyntheticDefaultImports": true,
        "isolatedModules": true
    }
}

run npx jest

Expected behavior

No TS errors

Actual behavior

Error: Jest: Failed to parse the TypeScript config file ./some_proj/jest.config.ts
  TSError: ⨯ Unable to compile TypeScript:
jest.config.ts:55:13 - error TS1343: The 'import.meta' meta-property is only allowed when the '--module' option is 'es2020', 'es2022', 'esnext', 'system', 'node12', or 'nodenext'.

console.log(import.meta)
               ~~~~~~~~~~~

    at readConfigFileAndSetRootDir (/some_proj/node_modules/jest-config/build/readConfigFileAndSetRootDir.js:136:13)
    at async readConfig (/some_proj/node_modules/jest-config/build/index.js:216:18)
    at async readConfigs (/some_proj/node_modules/jest-config/build/index.js:404:26)
    at async runCLI (/some_proj/node_modules/@jest/core/build/cli/index.js:140:59)
    at async Object.run (/some_proj/node_modules/jest-cli/build/cli/index.js:155:37)

Additional context

No response

Environment

System:
  OS: Linux 5.17.12-100.fc34.x86_64
  CPU: (8) arm64

Binaries:
  Node: 16.15.0
  npm: 7.20.0

npmPackages:
  "jest": "28.1.0",
  "ts-jest": "^28.0.5"

Stack overflow

There is a question on stackoverflow been posted 9 months ago still not answered...

TS Jest

issue on git

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[Torsitano]

Issue still present

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[Torsitano]

Issue still present

[SimenB]

Yeah, this isn't currently possible - see https://github.com/facebook/jest/issues/11453#issuecomment-1040424443. In #12397 we enforce CJS, might be we should tweak this. It's unfortunate this requires using a loader, tho... Would love to figure out a good way for Jest to just ask ts-node to load the config for us without caring about what flavour of module system it's written in

[Abhi347]

So is there any workaround for this? This is the only blocker I have for migrating my code to ESM from CJS.

[lvqq]

Any updates about this issue? Same error while using ts-jest and it blocks even if I use ts-node to import jest.config.ts

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[Lord-Valen]

Bump

[tim-g-provectusalgae]

Well this puts us in a bind...

[ologbonowiwi]

Any possible solution? If there's any, I can help with.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[Toliak]

Issue still present

[ashfaqnisar]

Any update on this ?

[ologbonowiwi]

Still present.

[thw0rted]

I think there's some confusion because the tsconfig used to compile jest.config.ts, before launching the test runner, is not necessarily the same tsconfig used by the ts-jest transformer to compile the TS code under test.

I don't write my Jest config in TS -- it works fine in JS with type annotation comment directives -- but for those who do, is there really a use-case for consuming import.meta while configuring Jest (i.e., specifically in jest.config.ts)?

As far as consuming import.meta in the code under test, I believe that should fall into the purview of ts-jest -- they punted over here specifically because you're trying to refer to it in the config file, before ts-jest actually does anything.

ETA: actually I don't think there is a problem on the ts-jest side. I just found https://github.com/kulshekhar/ts-jest/issues/3888 which links to this handy example, where the user is successfully running a test that uses import.meta, using ts-jest/presets/default-esm. So, bottom line, this issue is only about import.meta in jest.config.ts, specifically, and if you want to use import.meta in your code and/or tests, that already works. (Again, if you are trying to use import.meta in jest.config.ts, I would be really curious to know why.)

[thw0rted]

@SimenB if my logic in the previous comment is correct, then this should be closed now as a duplicate of https://github.com/facebook/jest/issues/13118 .

[MaverickH]

I don't use it specifically in the jest.config.ts file, but my project does use it in the globalSetup.ts file which has the same issue.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[Torsitano]

Issue still present

[AlfieJones]

@thw0rted The use case for me is in the globalSetup which has the same issue

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[pocesar]

still happens

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[DeepUmbrella]

still happens

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[khitrenovich]

Still relevant...

[vdo9]

Issue persists...

[gregorvand]

still happens

[tranphuquy19]

still happens