v7 fails in Jest, v6 works ok

[mataspetrikas]

Screenshot

Description

We have a Next.js TypeScript setup, using graphql-request v6.1.0, trying to update to v7.1.2

The app integration works ok, with no code changes. But - when running the unit tests, if a test imports any code that depends on the graphql-request, the jest fails with a following message:

    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.

...

    SyntaxError: Cannot use import statement outside a module
...

Did anyone encounter that error already? Any changes that can be added to jest.config maybe?
I have tried adding the library path to transformIgnorePatterns but that didn't help.

Downgrading back to v6 resolves it but I'd rather update to latest.

[mataspetrikas]

here's our jest config, just in case:

import type { JestConfigWithTsJest } from 'ts-jest';
const ignoredModules = ['next/server'].join('|');

const jestConfig: JestConfigWithTsJest = {
  preset: 'ts-jest/presets/js-with-ts',
  testPathIgnorePatterns: ['./.next/', './node_modules/'],
  setupFilesAfterEnv: ['./jest.setup.ts'],
  globalSetup: './jest.global-setup.ts',
  moduleDirectories: ['node_modules', __dirname],
  testEnvironment: 'jsdom',
  transform: {
    // '^.+\\.[tj]sx?$' to process js/ts with `ts-jest`
    // '^.+\\.m?[tj]sx?$' to process js/ts/mjs/mts with `ts-jest`
    '^.+\\.tsx?$': [
      'ts-jest',
      {
        tsconfig: './tsconfig.jest.json',
      },
    ],
    // mjs files will throw the `SyntaxError: Cannot use import statement outside a module` error by default
    '.*\\.mjs$': 'ts-jest',
  },
  transformIgnorePatterns: [`/node_modules/(?!${ignoredModules})`],
};

export default jestConfig;

[jasonkuhrt]

haven't read your issue yet but from the title this may be relevant #863