[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]

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]

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 #11453 (comment). 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]

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]

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

[github-actions]

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]

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]

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

[tiborux]

any news here?
I have the same problem

[adam-rocska]

srsly wtf

[roniceyemeli]

still persist

[cleve-fauna]

Hey peeps,

My teammate @macmv came up with a work around for this using jest transformers.

Feel free to use this code:

const tsJest = require("ts-jest").default;

module.exports = {
  createTransformer(config) {
    const transformer = tsJest.createTransformer(config);
    const tsProcess = transformer.process;
    transformer.process = (sourceText, ...rest) => {
      sourceText = sourceText.replaceAll("import.meta.env", "({} as any)");
      return tsProcess(sourceText, ...rest);
    };
    return transformer;
  },
};

The other nifty thing about this is you could extend it to install some kind of mock object instead of ({} as any) for example { taco: "tuesday", pizza: "friday" }.

Enjoy!

[github-actions]

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.

[adam-rocska]

Bump. Not stale. Ffs.

[psychobolt]

For Yarn PnP ESM projects, I managed to workaround by using my own ts-node register instead. Loaders is working well for Node 18.6+ If your project is on Node 18.6+, you can see my yarn patch for lines to modify.

diff --git a/build/readConfigFileAndSetRootDir.js b/build/readConfigFileAndSetRootDir.js
index e989961ba71bbea43eb293ebdc7739f00f6e85e7..44429f504f568cb5cef2998f527e0a8837d47338 100644
--- a/build/readConfigFileAndSetRootDir.js
+++ b/build/readConfigFileAndSetRootDir.js
@@ -11,6 +11,13 @@ function path() {
   };
   return data;
 }
+function url() {
+  const data = _interopRequireWildcard(require('url'));
+  url = function () {
+    return data;
+  };
+  return data;
+}
 function fs() {
   const data = _interopRequireWildcard(require('graceful-fs'));
   fs = function () {
@@ -101,7 +108,11 @@ async function readConfigFileAndSetRootDir(configPath) {
   let configObject;
   try {
     if (isTS) {
-      configObject = await loadTSConfigFile(configPath);
+      const configModule = await import(path().isAbsolute(configPath)
+        ? url().pathToFileURL(configPath).href
+        : configPath
+      );
+      configObject = configModule.default;
     } else if (isJSON) {
       const fileContent = fs().readFileSync(configPath, 'utf8');
       configObject = (0, _parseJson().default)(

Then using ts-node-esm loader to launch Jest CLI:

yarn node --loader ts-node/esm $(yarn bin jest) # or $(yarn bin test-storybook) # `file://` for resolving windows file paths

This should be able to read your project's tsconfig.json.

Update: I migrated the @swc-node/register/esm but the solution above should work similarly.

[mattgodbolt]

This seems to be rather a limitation in jest. I'm trying to port my mocha-based project to jest as I had thought it might have fewer issues with TypeScript and modules; but apparently not. Sometimes I wonder if anyone uses typescript and ECMAScript modules for anything as nothing seems to work; I've been on a multi-hour Google/SO/Github issue journey and nobody seems to have solved this

[magistrator]

this is the best solution I found
https://stackoverflow.com/questions/72128718/test-suite-failed-to-run-import-meta-env-vite
see first reply

[SimenB]

#15190 allows you to disable typechecking and overriding all other options (i.e., you can add /** @jest-config-loader-options {"compilerOptions": {"module": "esnext"}, "moduleTypes": null} */ to the config file).

Unfortunately, native ESM doesn't work with the transpilation, so you'll get an error about the import statements at runtime as we still load the file using require:

jest/packages/jest-config/src/readConfigFileAndSetRootDir.ts

Line 118 in ba74b7d

let configObject = interopRequireDefault(require(configPath)).default;

I don't think programmatic registration of ts-node works with native ESM?