Add sentry replays and source maps #6032
Conversation
github-actions
bot
added
scope: frontend
dependencies
dakotabenjamin
force-pushed
the
add/6006-sentry-replays
branch
from
d1f5fff
to
91d7efb
Compare
frontend/package.json
Outdated
| "@sentry/tracing": "^7.56.0", | ||
| "@sentry/react": "^7.60.1", | ||
| "@sentry/tracing": "^7.60.1", | ||
| "@sentry/browser": "^7.60.1", |
There was a problem hiding this comment.
I couldn't find any instances where @sentry/browser package is being utilized. From the React | Sentry Docs
All methods available in
@sentry/browsercan be imported from @sentry/react.
Since we are already using @sentry/react in our project, it might be a good idea to consider removing the unused @sentry/browser.
frontend/src/index.js
Outdated
| @@ -16,8 +16,22 @@ if (SENTRY_FRONTEND_DSN) { | |||
| Sentry.init({ | |||
| dsn: SENTRY_FRONTEND_DSN, | |||
| environment: ENVIRONMENT, | |||
| integrations: [new BrowserTracing()], | |||
| integrations: [ | |||
| new BrowserTracing(), | |||
There was a problem hiding this comment.
On a separate note (unrelated to the changes made in this PR), the BrowserTracing import from @sentry/tracing is now deprecated. It's recommended to directly import it from our framework-specific SDK, @sentry/react. This lets us remove the @sentry/tracing package altogether.
|
Kudos, SonarCloud Quality Gate passed!
|
This PR adds sentry replays and source maps for improved frontend tracking