Preserve error stack traces across contexts

[fregante]

1. content.js calls myGet()
2. myGet’s handler returns an error in the background page
3. content.js throws the error

Since the error was generated in the background page, its stack trace won't have any reference to myGet() nor its origin. Only the console will point to the throw Error inside the response handler, but nothing before that.

Maybe something like this will append the current stack trace to the error that was received:

  const error = deserializeError(response.error);
+ error.stack += Error.captureStackTrace();
  throw error;

or

• Optionally preserve current stack sindresorhus/serialize-error#98

[fregante]

I implemented this in my mini-library via Error#cause. In short, instead of deserializing the error and throwing it, I throw a new error and deserialize the other one into cause

https://github.com/fregante/webext-msg/blob/e8796cb1ecf5c81c3e07b9263a8223487df86760/index.ts#L30-L34

I think that in order to do the same here you'd have to drop the polyfill: Actually, not necessary

• Drop webextensions-polyfill to avoid unnecessary abstraction  #126