TypeScript declarations are not working when used with @jest/globals

[slavafomin]

Hello!

Thank you for this great library!

However, when using TypeScript and Jest with @jest/globals, the declarations provided by the package doesn't work. E.g.:

import 'jest-extended';

import { expect } from '@jest/globals';

// TS2339: Property toIncludeSameMembers does not exist on type
expect([]).toIncludeSameMembers([]);

Have you considered this use case? Thank you.

[int19h]

To make the asymmetric matchers visible, you can do the following in your globals.d.ts or equivalent:

import * as jestExtended from 'jest-extended';
type JestExtended = typeof jestExtended;
declare module 'expect' {
    interface AsymmetricMatchers extends JestExtended {}
}

However, this requires you to use asymmetric matching in all cases by using toEqual; e.g. for your original example:

expect([]).toEqual(expect.toIncludeSameMembers([]));

For regular matchers you can also kinda sorta do this:

declare module 'expect' {
    interface Matchers extends JestExtended {}
}

However the problem is that the object exported by jest-extended is of type CustomMatchers<any>, which results in expect() returning an object that allows arbitrary members, compromising type safety. If the package exported the generic CustomMatchers interface itself, alleviating the need for typeof, we could do:

import {CustomMatchers} from 'jest-extended';
declare module 'expect' {
    interface Matchers<R> extends CustomMatchers<R> {}
}

Of course, ideally, the package should just do this itself for both kinds of matchers.

[alexgwolff]

Working with TS 5.4+

// global.d.ts

declare module 'expect' {
  interface Matchers<R> extends CustomMatchers<R> {}
  interface AsymmetricMatchers extends CustomMatchers<unknown> {}
}

export {};