sindresorhus / is

Type check values
MIT License
1.68k stars 109 forks source link

Struggling to configure jest to compile `is` #201

Closed simPod closed 12 months ago

simPod commented 12 months ago

Hello, is there any chance anyone stumbled upon the same issue?

I installed is on the project. Everything works fine except jest tests.

I'm using "type": "module" in my package.json and jest won't compile is:

FAIL src/some.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:
    /builds/build-cache/yarn/cache/@sindresorhus-is-npm-6.1.0-d56260a06d-10c0.zip/node_modules/@sindresorhus/is/dist/index.js:270
    export function isAll(predicate, ...values) {
    ^^^^^^
    SyntaxError: Unexpected token 'export'
    > 1 | import is from '@sindresorhus/is';
        | ^
      2 |
      3 | const replaceMark = '__replace__';
      4 |
      at Runtime.createScriptFromCode (../../../../build-cache/yarn/cache/jest-runtime-npm-29.7.0-120fa64128-10c0.zip/node_modules/jest-runtime/build/index.js:1505:14)
      at Object.require (src/some.ts:1:1)
      at Object.<anonymous> (src/some.test.ts:1:1)

My jest config looks like this, it uses ts-jest:

/** @type {import('ts-jest').JestConfigWithTsJest} */
module.exports = {
  coverageReporters: ['text', 'cobertura'],
  extensionsToTreatAsEsm: ['.ts'],
  moduleNameMapper: {
    '^(\\.{1,2}/.*)\\.js$': '$1',
  },
  testEnvironment: 'jsdom',
  transform: {
    '^.+\\.tsx?$': [
      'ts-jest',
      {
        tsconfig: 'tsconfig-jest.json',
        useESM: true,
      },
    ],
  },
};
simPod commented 12 months ago

Ok I had this in my drawer for 2 weeks. When I finally decide to ask for help I find the solution.

I ditched ts-jest in favor of babel

/** @type {import('jest').Config} */
module.exports = {
  coverageReporters: ['text', 'cobertura'],
  extensionsToTreatAsEsm: ['.ts'],
  moduleNameMapper: {
    '^(\\.{1,2}/.*)\\.js$': '$1',
  },
  testEnvironment: 'jsdom',
  transform: {
    '\\.[tj]sx?$': ['babel-jest', { configFile: './babel.config.test.cjs' }],
  },
  transformIgnorePatterns: ['node_modules/(?!@sindresorhus)'],
};

babel config:

module.exports = {
  presets: [['@babel/preset-env', { targets: { node: 'current' } }], '@babel/preset-typescript'],
};