[🐛 Bug]: Typescript support for Custom matchers seems broken with V9

[wswebcreation]

Have you read the Contributing Guidelines on issues?

• [X] I have read the Contributing Guidelines on issues.

WebdriverIO Version

V9

Node.js Version

20

Mode

WDIO Testrunner

Which capabilities are you using?

No response

What happened?

When creating a new customer matcher and you want to use ExpectWebdriverIO.PartialMatcher you get a TS error Namespace 'global.ExpectWebdriverIO' has no exported member 'PartialMatcher'. This prevents the Visual Testing Service to upgrade to V9 without using a workaround. See also https://github.com/webdriverio/visual-testing/actions/runs/10442443274/job/28914748091?pr=417

What is your expected behavior?

No response

How to reproduce the bug.

Clone the Visual project and use this PR

Relevant log output

Namespace 'global.ExpectWebdriverIO' has no exported member 'PartialMatcher'

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• [X] I have searched the existing issues

[wdio-bot]

Thanks for reporting!

We greatly appreciate any contributions that help resolve the bug. While we understand that active contributors have their own priorities, we kindly request your assistance if you rely on this bug being fixed. We encourage you to take a look at our contribution guidelines or join our friendly Discord development server, where you can ask any questions you may have. Thank you for your support, and cheers!

[wswebcreation]

I cannot find the root cause, but it works in V8 without installing expect-webdriverio as a separate package. In V9 we miss the "automatic" link to this