Tom Mrazauskas

> I've made some assumptions about the type changes in #13247 and dynamically typecast Mocked to PropertyDescriptor to get things to work. Can spot this typecast ;D Could you point...

Checked out the branch and looked through your change. I think all is fine with types. Looks right for my eye.

Could you add type tests, please? For completeness and to make sure that generic types will work as expected for the user. The tests live in [this file](https://github.com/facebook/jest/blob/d712533f6d16ecf403b6eb81e88d2c955669c5d9/packages/jest-mock/__typetests__/mock-functions.test.ts#L251). To run...

Right, all looks good to me. So we have to wait for @SimenB, because only he is able to merge PRs.

Sure. I moved forward with refactoring `jest-haste-map`. That is tricky case. Will figure it out slowly.

Oh.. That’s to complicated to rebase and I can’t integrate it with haste module anyways. Leaving this for smarter than me (; Closing to have less noise around.

> We don't support Jest 28 yet, but we should soon. I see. So my idea might be premature. Just to add more detail. Jest v27.4 shipped with `jest.mocked()` helper...

Ready to merge

> What do people think? Adding support for the new config format is very good idea, but the amount of documentation is currently overwhelming. How do other plugins deal with...

Another though. If we have `const runner = (await import(runPath)).default`, is the following still needed: https://github.com/jest-community/create-jest-runner/blob/f474d84647a8a850b1f02ef80f4eecb96b3af703/lib/createJestRunner.ts#L103-L105