[Bug]: Top level await expressions are only ....

[vekexasia]

Version

29.1.1

Steps to reproduce

src/testasync.ts

await new Promise(() => 'a')
export const a = true

jest.config.cjs

/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {

  moduleNameMapper: {
    '(.+)\\.js$': '$1'
  },
  transform: {
    '^.+\\.ts$': ['ts-jest', {
      diagnostics: true,
      tsconfig: {
        module: 'nodenext',
        moduleResolution: 'bundler',
        target: 'es2017',
      },
      useESM: true,
      compiler: 'typescript',
    }]
  }
}

and a test file

import { a } from '../src/testasync'
describe('test', () => {
  it('should work', () => {
    expect(true).toBe(a)
  })
})
export {}

Expected behavior

test pass

Actual behavior

error TS1378: Top-level 'await' expressions are only allowed when the 'module' option is set to 'es2022', 'esnext', 'system', 'node16', or 'nodenext', and the 'target' option is set to 'es2017' or higher.

on
await new Promise(() => 'a')

Debug log

ts-jest.log

Additional context

CodeSandbox

Environment

System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 5800X3D 8-Core Processor
  Binaries:
    Node: 20.6.1 - ~/.nvm/versions/node/v20.6.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v20.6.1/bin/yarn
    npm: 9.8.1 - ~/.nvm/versions/node/v20.6.1/bin/npm
  npmPackages:
    jest: ^29.7.0 => 29.7.0

[uriva]

I think I have the same problem, here's my setup: https://stackoverflow.com/questions/77407758/top-level-await-with-jest-and-typescript

[vekexasia]

update on this?

[douglascayers]

Came across this problem myself tonight while trying to migrate a commonjs project to ESM.

No matter how I change my tsconfig.json target, module, and moduleResolution values to, the error always comes up. 😢

[alex-page]

I managed to fix this issue by setting up my jest config with useESM https://kulshekhar.github.io/ts-jest/docs/getting-started/options/useESM

[midnqp]

@alex-page Can you please share your entire jest config file?

I tried useESM but couldn't get it to work. My tsconfig contains { "module": "esnext", "target": "nodenext"}

My jest config is as follows.

{
  moduleNameMapper: {
    '^(\\.{1,2}/.*)\\.js$': '$1',
    '^@/(.*)\\.js$': '<rootDir>/src/$1.ts',
  },

  transform: {
    '^.+\\.(ts|tsx)?$': [
      'ts-jest', 
      { 
        useESM: true
      }
    ], 
  },
  
  testMatch: [ '<rootDir>/tests/**/*.test.ts'],
}

[midnqp]

Update 🎉 Adding the following line fixes this bug for me!

 extensionsToTreatAsEsm: [".ts"],

Ah, feels great. It's 3am now for me.