Property 'custom jest matcher' does not exist on type 'Matchers<R>' about expect-more

[aaronmcadam]

Yeah I think using the types directive has the same effect as using a global typings file. Thanks @JamieMason

[aaronmcadam]

As mentioned on the older project, I had to add the following to my tsconfig.json in order to avoid my hack and the type assertion:

"types": ["expect-more-jest", "jest"]

Is this the standard solution to ensure the types are loaded correctly?

[JamieMason]

Sorry for the slow reply @aaronmcadam, I managed to somehow unwatch some of my projects and stop getting notifications. I have run into the same problem and after looking into it found that it can be worked around by using a global.d.ts file in the root of my project that imports the packages VS Code otherwise cannot see.

https://github.com/JamieMason/expect-more/blob/expect-more-jest%402.3.0/global.d.ts

I hope this works for you too 🤞

I've also done some refactoring this weekend which will hopefully improve the intellisense output and how the typings are managed.