Fix typings of toThrowWithMessage, support unconstructable errors

[GerkinDev]

What

This PR fixes typings issues noted in #472, and adds support to unconstructable errors (such as abstract classes or not taking a message string as first arg) to be passed as error class.

Why

See #472. Moreover, toThrowWithMessage was unusable with AssertionError from the node assert module.

Notes

The matcher first tries to instantiate the type with the message (toStringed in case it was a regex).
If the instantiation fails, it creates a new Error on which it sets the name & message in order to be correctly printed as expected in the message.

Housekeeping

• Unit tests
• Documentation is up to date
• No additional lint warnings
• Typescript definitions are added/updated where relevant

[codecov]

Codecov Report

Merging #475 (7fa174d) into main (14830d5) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #475   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           71        71           
  Lines          575       582    +7     
  Branches       148       148           
=========================================
+ Hits           575       582    +7     

Impacted Files	Coverage Δ
src/matchers/toThrowWithMessage.js	100.00% <100.00%> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 14830d5...7fa174d. Read the comment docs.

[SimenB]

sweet, thanks!

[GerkinDev]

Hi @SimenB , do you know when this will be released ? I'm heavily relying on node assert and I can't test thrown errors correctly without this.

Thanks !

[SimenB]

https://github.com/jest-community/jest-extended/releases/tag/v3.0.2

[GerkinDev]

Thanks so much !