doc, types, test: Use Error objects instead of plain objects with replyWithError() - #2900

Thank you @okko!
The thing is that I'm still wondering if we should support plain object errors. IIRC, this is valid from the node perspective, also not sure how useful it really is.

Same here, I don't know what the use case for that would be, but can't rule it out. I would merge at least #2899 to document usage that better reflects what Node apparently does internally.

Then maybe wait with this #2900. On the other hand, reverting this is super easy if someone presents a use case.

@okko can you please:

1. Fix the format
2. Remove the support for
3. Remove the skipped test (or add one with an error object if it does not already exist, please)

@mikicho Thanks! I fixed formatting and enabled the test. I didn't get the 2nd point of your comment, was there a word missing?

🎉 This PR is included in version 15.0.0-beta.8 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀