nodejs.util.inspect.custom support for uncaught Errors

[underflow00]

What is the problem this feature will solve?

When an Error/object is thrown and not caught, the error information printed to the terminal does not consider the [Symbol.for("nodejs.util.inspect.custom")]() function. https://nodejs.org/api/util.html#utilinspectcustom
This is potentially a bug.

class C1 {
    [Symbol.for("nodejs.util.inspect.custom")]() {
        return "custom string";
    }
}
console.log(new C1()); // custom string appears
throw new C1() // custom string does not appear

What is the feature you are proposing to solve the problem?

Add nodejs.util.inspect.custom function support for uncaught Errors

What alternatives have you considered?

No response

[BridgeAR]

AFAIC it is intentional to not trigger custom inspection in case of a crash. The reason is that a crash is probably not anticipated and custom inspection could hide details. It could also add more, so it's definitely a trade-off. It would theoretically be possible to log both but the question is also how to print that.