In our app, we change the Error.prepareStackTrace to suit our needs.
Once we started using Bristol, which is awesome by the way, we started to have erratic stack traces. Our debugging revealed that Bristol was replacing our method with the original one, leaving us with vanilla stack traces.
So, in order to use Bristol, we had to make that change. We'd be more than happy to keep using your version instead of our fork, if you make us the honour to include that change in the npm version.
TomFrost
commented
7 years ago
In our app, we change the Error.prepareStackTrace to suit our needs.
Once we started using Bristol, which is awesome by the way, we started to have erratic stack traces. Our debugging revealed that Bristol was replacing our method with the original one, leaving us with vanilla stack traces.
So, in order to use Bristol, we had to make that change. We'd be more than happy to keep using your version instead of our fork, if you make us the honour to include that change in the npm version.