Matt Phillips

Thanks @Coridyn sorry for the delay in getting this merged!

Thanks for your messages, this package isn't abandoned. I've just published https://www.npmjs.com/package/jest-expect-message/v/1.0.4 which includes fixes for #39 and #24 and #34. I'll go ahead and close this issue 👍

Going to close as this can be solved with https://github.com/mattphillips/jest-expect-message/issues/26#issuecomment-803660589 or by following the Typescript setup outlined in the [readme](https://github.com/mattphillips/jest-expect-message#configure-typescript)

Hey @amercier thanks for raising this, I wasn't aware of this error inside of Jest 😄 This one will be super hard to solve in userland and feels like potentially...

Nice idea @swa1ps, thanks!

Hi @mjafari98 thanks for the PR, I'm not sure this is something we will want to support. However I've just added support for disabling the custom message prefix which means...

Thanks for raising the issue, this is fixed in: https://www.npmjs.com/package/jest-expect-message/v/1.1.2

Hey guys sorry for the delay in coming back to this, I’m currently holidaying and AFK for the most-part. @benjaminkay93 I think this should be possible with the new async...

@benjaminkay93 check out the expect extend docs there is an async section https://jestjs.io/docs/en/expect#expectextendmatchers Let me know how you get on with this, if you need a hand I’ll be back...

Sounds great! Feel free to send a PR with this, just drop a note here if you are working on it :smile: