Tom Mrazauskas

Fix it. Just open a PR (;

Most probably you should build the repo and all will work. By the way, to test the change you should write type tests. The type tests for matchers live here:...

Similar change was made in `@types/jest` some time ago and had to be reverted. For discussion see https://github.com/DefinitelyTyped/DefinitelyTyped/discussions/62128

One can use type arguments for extra type safety as well. I think we could agree that there is no consensus on this feature and that is why it is...

Usually I run slow e2e tests separately from unit tests. In this setup `vscode-jest` could be told to rerun only unit tests. --- The other problem you talk about needs...

Actually, no need to have any option or to wrestle with the Compiler API and no need to involve `ts-jest` too: ```ts import {expect} from 'jest-strictly-typed-expect'; ``` Could work like...

Changes in this repo will have no effect on Playwright’s `.toBe()` typings, because they keep a hard copy here: https://github.com/microsoft/playwright/blob/da87a0af76d244b977a13702dff86a004890ba99/packages/playwright-test/types/test.d.ts#L3816 --- After #13848 it should be possible to redeclare matcher...

Did you try skipping `rootDir` token in `testMatch` globs? That’s a path and because of path separators it might create different patterns in Windows and MacOS. As you know, globs...

Interesting. Did you check if patterns from [the documentation](https://jestjs.io/docs/configuration#testmatch-arraystring) are working on Windows?

> > Interesting. Did you check if patterns from [the documentation](https://jestjs.io/docs/configuration#testmatch-arraystring) are working on Windows? > > Yes, it works That’s good news. If you have a working pattern, you...