fix: add Error prefix to Error objects names

[hoxyq]

This fixes printing Error objects in Chrome DevTools.

I've observed that Chrome DevTools is not source mapping and linkifying URLs, when was running this on larger apps. Chrome DevTools talks to V8 via Chrome DevTools protocol, every object has a corresponding RemoteObject.

When Chrome DevTools sees that Error object is printed in the console, it will try to prettify it. description field of the corresponding RemoteObject for the Error JavaScript object is a combination of Error name, message, stack fields. This is not just a raw stack field, so our prefix for this field just doesn't work. V8 is actually filtering out first line of the stack field, it only keeps the stack frames as a string, and then this gets prefixed by name and message fields, if they are available. As an illustration, this:

const fakeError = new Error('');
fakeError.name = 'Stack';
fakeError.stack = 'Error Stack:' + stack;

will be formatted by V8 as this RemoteObject:

{
  ...
  description: 'Stack: ...',
  ...
}

Notice that there is no Error prefix, that was previously added. Because of this, Chrome DevTools won't even try to symbolicate the stack, because it doesn't have such prefix.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
react-compiler-playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 16, 2024 4:28pm

[EdmondChuiHW]

Discussed offline.

Thanks for making sure the surrounding comments are up-to-date and the browser-specific impl are captured! 🙌