Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Sentry packages still bundled despite removal of initialization
- Removed Sentry dependencies and all remaining Sentry imports/usages in both UIs, replacing error boundaries with react-error-boundary and removing disabled init entrypoints so the SDK is no longer bundled.
Or push these changes by commenting:
@cursor push 64ce0a58e1
This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 6e6510e. Configure here.
| import { BrowserTracing } from '@sentry/tracing'; | ||
|
|
||
| import config from './config'; | ||
|
|
There was a problem hiding this comment.
Sentry packages still bundled despite removal of initialization
Medium Severity
Sentry initialization is disabled but @sentry/react and @sentry/tracing remain as dependencies in both gds-admin-ui/package.json and gds-user-ui/package.json. Multiple source files still actively import and use Sentry APIs: captureException in three admin UI components, Sentry.withProfiler(App) wrapping the entire user UI app tree in App.tsx, and Sentry.ErrorBoundary in several user UI components. These are now dead code, and the ~200KB Sentry SDK is still included in the production bundles despite serving no purpose.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit 6e6510e. Configure here.
1 participant
Scope of changes
Removes sentry from our React web UIs.
Type of change
Acceptance criteria
This PR will be merged without review.
Author checklist
Note
Medium Risk
Low code-change complexity, but it removes Sentry initialization and all Sentry-related build/env wiring, reducing production error/performance visibility and potentially affecting any workflows that relied on those env vars.
Overview
Disables Sentry across both React UIs (user + admin). The Sentry initialization modules in
web/gds-user-uiandweb/gds-admin-uiare reduced to a no-op/log message instead of configuring@sentry/*.Removes Sentry configuration from build/deploy plumbing. All
REACT_APP_SENTRY_*variables and build args are stripped from.envtemplates, Dockerfiles,docker-compose.yaml, the container build script, and GitHub Actions workflows (including staging), so UI images are no longer built with Sentry DSNs/environments.Reviewed by Cursor Bugbot for commit 6e6510e. Configure here.