stackdriver-errors-js
stackdriver-errors-js copied to clipboard
Client-side JavaScript exception reporting library for Cloud Error Reporting
Currently requiring `stackdriver-errors-js` results in quite a lot of code being pulled in -- it's one of our largest dependencies. The above is generated using https://github.com/webpack-contrib/webpack-bundle-analyzer. Stat Size: 136.64KB (before...
Hi, I have code that does: ``` // In a promise `then` handler: myRegister(new Error('some error')); // ... // Elsewhere in the code: errorHandler.report(theNewError); ``` but the stackdriver API response...
I tried generating a new version with `npm run dist`, but I got: ``` $ npm run dist > [email protected] dist /workspaces/stackdriver-errors-js > gulp lib-concat fs.js:45 } = primordials; ^...
Not sure how should I solve if I wan't to send with error additinal info about user context, for example, current **browser window size**? I thought it could be added...
Are there any plans for this to be out of experimental mode and considered production ready?
## As is * Using Angular * Make a service request, throw a 500`HttpErrorResponse` * Report this error with `StackdriverErrorHandler` * Get a 400 from the service, error never reported...
I'm not sure if this is within the scope of this project or not. But I did notice that different browsers will have different error strings for the same error....
Setting up this module hides errors from the Chrome console. This is not good for debugging
![image](https://user-images.githubusercontent.com/1343284/59149595-9c3d0080-8a49-11e9-86f2-7db91ecc01b9.png) I have a bug in production (3rd error), the surrounding first 2 and latter 2 are mysterious to me. Can anyone explain further?