Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

All console errors show generated from @sentry/browser/esm/integrations/breadcrumbs.js:81

See original GitHub issue

[ x] Review the documentation: https://docs.sentry.io/
[ x] Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
[x ] Use the latest release: https://github.com/getsentry/sentry-javascript/releases
Provide a link to the affected event from your Sentry account

Package + Version

[ ^5.6.2] @sentry/browser
[^5.6.2 ] @sentry/node
raven-js
raven-node (raven for node)
other:

Description

Chrome dev console shows all output as from @sentry/browser/esm/integrations/breadcrumbs.js:81 - I’m using the @sentry/webpack-plugin but that’s only loaded in production. Curious if this is normal, and if so, how to get the line of code which triggered the log instead.

Issue Analytics

State:
Created 4 years ago
Comments:6 (2 by maintainers)

Top GitHub Comments

1reaction

jgentescommented, Nov 29, 2019

That did it, thank you for your help!

1reaction

kamilogorekcommented, Nov 29, 2019

@jgentes Breadcrumbs are platform-specific integrations, where ExtraErrorData is generic for any JS plaform, see: https://docs.sentry.io/platforms/javascript/#sdk-integrations vs. https://docs.sentry.io/platforms/javascript/#pluggable-integrations

This means that ExtraErrorData lives inside @sentry/integrations and is correctly required by you in the example above, but Breadcrumbs lives in the SDK itself under Sentry.Integrations.Breadcrumbs.