Jest fails to run tests with suretype

[Maxim Palenov]

After including suretype@3.3.0 into the project Jest fails to run unit tests with it.

Jest config:

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

The error:

  ● Test suite failed to run

    Jest encountered an unexpected token

    This usually means that you are trying to import a file which Jest cannot parse, e.g. it's not plain JavaScript.

    By default, if Jest sees a Babel config, it will use that to transform your files, ignoring "node_modules".

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/en/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/en/configuration.html

    Details:

    /.../node_modules/suretype/dist/index-nodejs.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,global,jest){import "./json-schema-nodejs.js";

[Gustaf Räntilä]

That should've been since 3.0.0 which changed the package to be Pure ESM.

The situation with Jest/TypeScript/ESM is really a mess. Sindre's gist on it might be helpful, and a ton of searching for what people do.

Or have a look at how this package does it (the package.json, jest.config.js and babel.config.cjs)