Tom Mrazauskas
Tom Mrazauskas
Makes sense. Probably this should wait for ESM support in `jest-worker`.
Sure. It would be great to improve the docs.
@bakkot Just added `ParseArgs`. That is really good idea. Thanks!
One `parseArgs` type is already exported and it is prefixed: https://github.com/DefinitelyTyped/DefinitelyTyped/blob/c8c035fce345dd72e240f9e1e3ded1ca5118e1f1/types/node/util.d.ts#L1159 Perhaps `ParseArgsTokens` looks better than just `Tokens`? The rest is just repetition of the same pattern. I think it...
Found better solution for my use case. No interest in this change anymore. Also does not seem there is interest from maintains side as well (;
Just to add: since Jest v28 the above should work equally with `declare module 'expect'` or `declare module '@jest/expect'`. By the way, it might be a good idea to include...
The [workerthreads](https://jestjs.io/docs/configuration#workerthreads) configuration option might help. It is a new feature which was shipped yesterday with [Jest v29.5](https://github.com/facebook/jest/releases/tag/v29.5.0). Note that this is **!!! strictly experimental !!!** and wasn’t tryout widely...
Can not reproduce this. Tried Jest 26 and higher versions.
`assert.equal()` and `assert.strictEqual()` are failing with "Compared values have no visual difference" instead of "serializes to the same string". `JSON.stringify()` does not show extra props just like `toMatchInlineSnapshot()`. I can...
@abhi-works Could you tell Jest and TS version you are using? If I remember it right, the type arguments if the `Matchers` interface differ between versions of Jest. That might...