Pass complete serialized errors between background and proxy store

[jlalmes]

I've been facing the issue where webext-redux only allows you to error.message back to my content scripts in the case of an error in an aliased action. However my error objects contain other information, for example:

Error {
  message: 'this is a message',
  status: 400,
  code: 'CODE-001',
  result: { ... },
  stack: { ... },
}

This pull request will serialize all errors by default, the full error is then reconciled and rejected to the content-script that called the original dispatch function. You can test this PR with this npm module webext-redux-w-errors@latest.

First-time contributor, open to any feedback! 🙌

[jlalmes]

@tshaddix @vhmth - Hi guys seeking some guidance here. I am dispatching async actions with aliases and am therefore needing to return the full payload of a rejected error back to the content script via the proxy store. Are you happy to merge and publish this?

[vhmth]

Thank you for contributing here! 🙏 Just a heads up the reason @tshaddix and I tend to be slow to reply is because our jobs are both extremely demanding. I'm really sorry about the lag here!

This seems very reasonable, and I'm very appreciative of this for the Loom extension itself. Just looked through the code to see where else errors are dispatched, but it seems this is the main throughpoint.

cc @tshaddix any thoughts here?

Before we land, could you check out the tests folder and add an appropriate test there that checks that an error can be dispatched properly and received in an expected manner?

https://github.com/tshaddix/webext-redux/tree/master/test

[vhmth]

Could we change back the name here and in package.json?