bc5ad749f7
Summary: We had our stack traces broken for a long time. They always pointed at the bundle.js file. With this change the stack traces **in the console** will be pointing at the actual source files. This will save a lot of time for engineers instead of manually looking for the source of errors. Why this didn't work before? When we were calling `console.error(error.toString())` the browser was not applying sourcemaps to the stacktrace as it interpreted as a random string. However, when you pass an actual instance of Error constructor, the sourcemaps will be applied and we get correct stack traces to the source files. I looked at the code of the Logger and it is already handles the Error instances, so I think this should be fine also for the logs that go to scuba. CC passy Reviewed By: LukeDefeo, passy Differential Revision: D49275025 fbshipit-source-id: 2addc601f45622e35890d7d0e1992f4bca41a338
flipper-ui-core (TBD)
Flipper's UI, agnostic of Electron vs Browser.