Revert "performance patch"

[Uzlopak]

As discussed in nodejs/node#42042 (comment) it seems that the performance improvement has some implications and should be reverted.

[mcollina]

For this specific module I think we are ok. We are not hitting any of the other constraints around inheritance here.

[xtx1130]

I'm +1 with mcollina. This package is just a Error standard implementation. See : Error() constructor. Use new to create an error or just use Error() is supported, and both initializations will trigger new.target.

[mcollina]

I would arguably say that's better to move the error to class and be done with it.

[Uzlopak]

just for clarification:

This PR is not a critique on the implementation. It is good that we can discuss this issue and have an active decision to apply or reject this PR.

[xtx1130]

@mcollina It can't move to class , because use class can't implement Error() method. class just can call with new.

[mcollina]

@mcollina It can't move to class , because use class can't implement Error() method. class just can call with new.

I'll just bump the major version and remove that feature.

[xtx1130]

If you ensure to drop the support of Error(). I can send a PR for fastify-error recently and will move the error to class

[mcollina]

Let's go with that, it seems the right thing to do given the subject and perf boost.