Description

• closes Type error on mockImplementation with call signature in object type #6155 (broken in v2.0.0)
• closes TypeScript errors when mocking overloaded functions #6182 (broken in v2.0.3)

Previously we had mockImplementation(fn: T) where T extends (...args: any[]) => any, but such T can include arbitrary overload and union types, so it looks like it's important to have singly picked function type (...args: Paramters<T>) => ReturnType<T> for the most reasonable usability.

There are probably two ways to solve this. One way is like this PR to NormalizedPrecedure<T> inside MockInstance<T>. Another way which Jest does is to have a wrapper SpiedFunction<T> for MockInstance<(...args: Parameters<T>) => ReturnType<T>>.

I think what Jest does still have issues left (though I'm not sure if it's intentional or not). For example, SpiedFunction doesn't cover the case of vi.mocked helper, so it would fail the example from OP #6155. So, I thought it's more robust to go with the former approach.

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.