Typescript error when importing jest-extended

Bug

jest-extended version: 1.0.0

.ts file:

import * as matchers from "jest-extended";

I get error: File ‘…/node_modules/jest-extended/types/index.d.ts’ is not a module.

Also, after upgrading to 1.0.0 unassigned import does not work any more:

import "jest-extended";

So: Unassigned import stoped working in version 1.0.0 And wildcard import does not work in typescript because of invalid .d.ts file.

[Ashlook]

Had the same issue here when migrating to (ts-)jest 27 and jext-extended 1.0.0.

Before

I have in global.d.ts :

import 'jest-extended';

In jest.config.ts :

/* ... */
setupFilesAfterEnv: ['jest-extended'],
/* ... */

After

I just changed my jest.config.ts and add /all :

/* ... */
setupFilesAfterEnv: ['jest-extended/all'],
/* ... */

Everything seems to work fine with this change, like @silverwind pointed.

[merrywhether]

This was my fix:

// tsconfig.json (note that this shouldn't also be your build config)
  "include": [
    ...,
    "setupTestsAfterEnv.ts"
  ],

// jest.config.js
{
  ...,
  setupFilesAfterEnv: ['./setupTestsAfterEnv.ts'],
}

// setupTestsAfterEnv.ts

// import main for types & /all for matcher auto-registration
import 'jest-extended';
import 'jest-extended/all';

Importing jest-extended is all TS needs to get it to register the types, and you only have to import it once in your project. This does not however cause anything JS-related to actually happen, and you can’t really work with the exports of jest-extended because they aren’t in the type defs.

Importing jest-extended/all causes the auto-registration of all of the matchers, but doesn’t do anything types-wise. TS will allow un-typed imports like that though, since the side-effects aren’t modeled in TS’s type system.

A bit of bummer to need the two imports, but it’s easier than other solutions.