chore(comps): remove Sentry integration - #1725
Open
carsonfarmer wants to merge 2 commits into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📊 Test Coverage Report
|
This was referenced Jul 27, 2026
Sentry is no longer actively monitored. Remove the Next.js instrumentation (client, server, and edge init), session replay, the withSentryConfig build wrapper (source map upload, /monitoring tunnel route, React component annotation), and all capture call sites. The user-facing error categorization and messages in error-handling.ts and airdrop-error-handling.ts are preserved; errors are now logged to the console instead of Sentry. global-error.tsx existed only to report to Sentry, so it is removed in favor of the Next.js default error page. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Same treatment as the posthog PR: the regenerated lockfile had re-resolved the @babel/core peer for eight surviving packages (next, styled-jsx, styled-components, connectkit, and friends) from 7.28.0 to 7.28.4 and picked up registry deprecation metadata. Rebuild from main's lockfile, removing only the @sentry/nextjs importer entry and entries unreachable from the remaining importers, so every surviving resolution is byte-identical to main. Verified with a frozen-lockfile install and a comps build. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
carsonfarmer
force-pushed
the
chore/remove-sentry-comps
branch
from
July 29, 2026 04:18
8b154e2 to
43b679b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Removes the Sentry integration from the comps app (part of winding down Sentry since we no longer actively monitor it). Companion PRs handle the API/services and load-test packages so each can be reviewed independently.
Changes
instrumentation.ts,instrumentation-client.ts(client init incl. session replay),sentry.server.config.ts,sentry.edge.config.tslib/sentry-config.ts(sampling/filtering helpers) andtypes/sentry.tswithSentryConfiginnext.config.mjs— this also removes the/monitoringtunnel route (browser events proxied through our server to dodge ad-blockers), build-time source map handling, and React component annotation, which should modestly speed up builds and shrink the client bundleapp/global-error.tsx— it existed solely to report root-layout errors to Sentry; without it Next.js renders its equivalent default error pagelib/error-handling.ts/lib/airdrop-error-handling.ts: all error categorization and user-facing messages preserved; full error context now goes toconsole.errorinstead of Sentryproviders/session-provider.tsx: both capture sites already had adjacentconsole.error/console.warncalls with the same context, so only the Sentry calls were removed@sentry/nextjsdependency and update the lockfile.env.example,apps/comps/turbo.json(NEXT_PUBLIC_SENTRY_DSN,SENTRY_AUTH_TOKEN,SENTRY_ORG,SENTRY_PROJECT, andNEXT_RUNTIMEwhich only the deleted instrumentation read), and rootturbo.json(NEXT_PUBLIC_SENTRY_DSN,SENTRY_NAVIGATION_SAMPLE_RATE)API/server-side Sentry env vars in root
turbo.jsonare intentionally left for the companion API/services PR.Trade-off to be aware of
After this merges, frontend errors are no longer aggregated anywhere — visibility is limited to Vercel runtime logs (server-side) and users' browser consoles (client-side). Session replay goes away entirely. This is the accepted trade-off since nobody is monitoring Sentry today.
Verification
pnpm --filter comps lint✅pnpm turbo build --filter=comps✅pnpm lint && pnpm format:check && pnpm build) ✅The Sentry SDK already no-ops when its DSN env vars are unset, so this PR is safe to deploy in any order relative to the env var cleanup below.
This PR intentionally touches code only:
NEXT_PUBLIC_SENTRY_DSN,SENTRY_DSN,SENTRY_ENVIRONMENT,SENTRY_AUTH_TOKEN,SENTRY_ORG,SENTRY_PROJECT.competitions-appproject once this is deployed. Full subscription cancellation should wait until the companion API/services and load-test PRs land.competitions-appSentry project before deleting it.🤖 Generated with Claude Code