MockFunction return type may be generic

[cawa-93]

esmock/src/esmock.d.ts

Line 9 in 28cbda5

type MockFunction = {

It allows you type mocked module like so:

const myModule = await esmock<typeof import('/module/path')>('/module/path')

[cawa-93]

cc: @jsejcksn

[iambumblehead]

is the issue that, the new typescript types file is forcing you to define <typeof import('/module/path')>? should we revert the esmock.d.ts?

[cawa-93]

No. It's enhansment. Currently esmock('module/path') return any and user will not get code intellisense. Type resolution from module may be automated if microsoft/TypeScript#31090 will be resolved.

Actually, I just realise, that user can set type just like: 🤦🏻‍♂️

const myModule: typeof import('/module/path') = await esmock('/module/path')

So, I close this as no actual, until microsoft/TypeScript#31090 was resolved

[iambumblehead]

@cawa-93 thanks for sharing that is great