feat(node): Improve non-error messages

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.

[timfish]

Closes#6822

This PR changes the messages reported for captured non-Error exceptions.

For the browser PR, it was decided not to use the class name due to these being mangled by bundling. Does this apply to node too?

[mydea]

This is def. an improvement already. I guess it is less likely to have minified class names in node, but still possible? But IMHO we can merge this in and still think about making this better for node if possible.

[AbhiPrasad]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

[mydea]

it was decided to to use the class name due to these being mangled by bundling. Does this apply to node too?

yes, since node can be minified (common for serverless) and minified js has performance benefits even for server runtimes.

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

I guess it would already be a possible improvement to just detect name and/or message and use these, if available?

[timfish]

As an aside, I wonder if we can detect if object has an name, message, and stack and turn it into an error. Thoughts?

Ok, I'll add that and some tests.

It worth noting that it already attempts to parse the stack property for any kind of object.