After upgrading to ts-jest 27: SyntaxError: Cannot use import statement outside a module

[doberkofler]

💥 Regression Report

> test@1.0.0 test
> jest --no-cache

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

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /Users/doberkofler/MyDev/ljs_app/trunk/examples/frontend/jest/jest27/src/setup-jest.ts:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import { hello } from './hello';
                                                                                      ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (node_modules/jest-runtime/build/index.js:1479:14)
      at async TestScheduler.scheduleTests (node_modules/@jest/core/build/TestScheduler.js:347:13)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        1.759 s
Ran all test suites.

Last working version

Worked up to version: 26.5.6

Stopped working in version: 27.0.0

To Reproduce

Steps to reproduce the behavior: npm test

Expected behavior

Link to repo (highly encouraged)

jest27.zip

Debug log:

ts-jest.log

envinfo

System:
    OS: macOS 11.3

Npm packages:
    jest: 27.0.1
    ts-jest: 27.0.0
    typescript: 4.2.4
    babel(optional):

[ericvera]

Is this fix already in 27.0.3? I am seeing the same issue (tests worked with 26.* and no longer work with 27 with "Cannot use import statement outside a module").

[ahnpnl]

This should be fixed already, you can try clearing jest cache.

[ericvera]

I tried that (just tried it again to be sure) and still no luck.

[ahnpnl]

would you pls share a reproduce repo?

[ericvera]

Unfortunately, it is a somewhat complex project so extracting a small enough repro is not trivial. Here is the config in case it raises some flags. Otherwise, I'll get back with a repro once I have a chance to work on one.

// package.json extract

"jest": {
    "preset": "ts-jest",
    "testEnvironment": "jsdom",
    "testPathIgnorePatterns": [
      "dist",
      "jest.setup.ts",
      "test-utils.tsx"
    ],
    "setupFilesAfterEnv": [
      "./src/__tests__/jest.setup.ts"
    ],
    "moduleNameMapper": {
      "\\.(css)$": "identity-obj-proxy",
      "^@project-name/(.*)/(.*)/(.*)$": "<rootDir>/../../packages/$1/src/$2/$3",
      "^@project-name/(.*)/(.*)$": "<rootDir>/../../packages/$1/src/$2",
      "^@project-name/(.*)$": "<rootDir>/../../packages/$1/src"
    },
    "globals": {
      "ts-jest": {
        "tsconfig": {
          "jsx": "preserve"
        },
        "babelConfig": {
          "presets": [
            "next/babel"
          ],
          "plugins": [
            "macros"
          ]
        }
      }
    }
  }

[alan-cooney]

Also having this issue with next/babel enabled as well

[ericvera]

I have around 20 modules in my monorepo and I can confirm that only modules that use next/babel have the problem.

[feitian124]

same issue here, an simple ts project without babel with default config

module.exports = {
    preset: 'ts-jest',
    testEnvironment: 'node',
};

the error

SyntaxError: Cannot use import statement outside a module

[mnik01]

same issue

[Edweis]

Same

[Yifei-G]

Same issue here!

[alan-cooney]

UPDATED

ts-jest doesn't understand the tsconfig compilerOptions setting for jsx of "preserve", but this is required for next. Therefore the best thing to do is override it just for jest in your jest config:

module.exports = {
  globals: {
    // This is necessary because next.js forces { "jsx": "preserve" }, but ts-jest requires { "jsx": "react-jsx" }
    'ts-jest': {
      tsconfig: {
        jsx: 'react-jsx',
      },
    },
  },
  //...
};

[edaqa-uncountable]

I was getting this error, but not using next/babel. I managed to get my tests to work with this config:

/** @type {import('@ts-jest/dist/types').InitialOptionsTsJest} */
module.exports = {
  preset: "ts-jest",
  testEnvironment: "node",
  globals: {
    "ts-jest": {
      isolatedModules: true,
    },
  },
  transform: {
    "^.+\\.jsx?$": "babel-jest",
  },
  moduleNameMapper: {

  },
  moduleDirectories: ["js", ".", "node_modules"],
}

[hutber]

module.exports = {
preset: "ts-jest",
testEnvironment: "node",
globals: {
"ts-jest": {
isolatedModules: true,
},
},
transform: {
"^.+\.jsx?$": "babel-jest",
},
moduleNameMapper: {

},
moduleDirectories: ["js", ".", "node_modules"],
}

Which file is this sorry?

[alan-cooney]

That's the jest config file

[JeanJPNM]

Hi, I'm facing the same issue, but none of the solutions have worked for me.

Here are my relevant configurations:

tsconfig.json

{
  "compilerOptions": {
    "alwaysStrict": true,
    "allowSyntheticDefaultImports": true,
    "declaration": true,
    "downlevelIteration": true,
    "esModuleInterop": true,
    "isolatedModules": true,
    "lib": ["ES2020", "DOM.Iterable"],
    "module": "CommonJS",
    "moduleResolution": "Node",
    "noImplicitAny": true,
    "noImplicitOverride": true,
    "noImplicitThis": true,
    "outDir": "dist/cjs",
    "sourceMap": true,
    "strict": true,
    "stripInternal": true,
    "target": "ES2019"
  },
  "exclude": ["**/*.(spec|test).ts", "node_modules"],
  "include": ["src/*"]
}

package.json

{
  "type": "module",
  // ...
  "devDependencies": {
    "jest": "^27.5.0",
    "ts-jest": "^27.1.3",
    // ...
  }
}

jest.config.js

/** @type {import("@jest/types").Config.InitialOptions} */
const config = {
  preset: 'ts-jest',
  roots: ['<rootDir>/src'],
}

export default config

[zgrybus]

@JeanJPNM This one works for me:

jest.config.json

{
  "preset": "ts-jest",
  "testEnvironment": "jsdom",
  "moduleFileExtensions": ["ts", "tsx", "js", "jsx", "json", "node"],
  "roots": [
    "src"
  ],
  "testRegex": "(/__tests__/.*|(\\.|/)(test|spec))\\.(tsx)$",
  "transform": {
    "^.+\\.tsx$": "ts-jest"
  },
  "moduleNameMapper": {
    "src/(.*)": "<rootDir>/src/$1"
  }
}

package.json

{
  // ...
  "devDependencies": {
   "@types/jest": "^27.4.0",
    "jest": "^27.5.1",
    "ts-jest": "^27.1.3",
    // ...
  }
}

[alex-tsx]

In my case jest would stumle on .js files from one of the dependencies in node_modules with SyntaxError: Cannot use import statement outside a module.

I had to make sure, that ts-jest wouldn't ignore (when transforming) .js files in troublesome dependency.

After reading carefully about presets, I realized, that it leaves them 'as-is' with preset: 'ts-jest'. I changed it to preset: 'ts-jest/presets/js-with-ts' and set "allowJs": true in tsconfig.json.

To not mess up my project's tsconfig.json, I have a separate one for jest.

In the end, my jest.config.js looks mainly like this:

module.exports = {
	preset: 'ts-jest/presets/js-with-ts',
	testEnvironment: "node",
	globals: {
		'ts-jest': {
			tsconfig: '<rootDir>/test/tsconfig.json',
		},
	},
	transformIgnorePatterns: [
		"node_modules/(?!troublesome-dependency/.*)",
	],
}

P.S. I didn't need a transform field, since the preset is already on it.

P.P.S. I didn't need to introduce any babel configuration

[linonetwo]

Adding 

  globals: {
    'ts-jest': {
      isolatedModules: true,
    },
  },

works.

My setup:

jest.config.js

/* eslint-disable unicorn/prefer-module */
/** @type {import('ts-jest/dist/types').InitialOptionsTsJest} */
module.exports = {
  preset: 'ts-jest',
  transform: {
    '\\.[jt]sx?$': 'ts-jest',
  },
  testEnvironment: 'node',
  setupFilesAfterEnv: ['./test/jest.setup.ts'],
  extensionsToTreatAsEsm: ['.ts'],
  globals: {
    'ts-jest': {
      useESM: true,
      isolatedModules: true,
    },
  },
};

package.json

  "scripts": {
    "test": "NODE_OPTIONS=--experimental-vm-modules jest --config=jest.config.js",

Before the change, I get lots of error, or just hang there stops running:

 FAIL  test/wikiast-util-to-wikitext.test.ts
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    slate-write/node_modules/unist-util-parents/index.js:16
    export function parents(tree) {
    ^^^^^^

    SyntaxError: Unexpected token 'export'

      1 | import cloneDeep from 'lodash/cloneDeep';
      2 | import type { IParseTreeNode } from 'tiddlywiki';
    > 3 | import { parents } from 'unist-util-parents';

And now "ts-jest": "28.0.2", works very well.

[PascalPixel]

For me what works;

module.exports = {
  preset: "ts-jest/presets/default-esm",
  testEnvironment: "node",
  extensionsToTreatAsEsm: [".ts"],
};

And run with;
"test": "NODE_OPTIONS=--experimental-vm-modules jest",

No other changes to the default installation, thanks @linonetwo