chore: remove Sentry and Spotlight integration#116
Merged
CaseyHoover merged 1 commit intomainfrom May 9, 2026
Merged
Conversation
Sentry's Next.js + Node SDKs caused severe dev-server slowdowns (10s UND_ERR_CONNECT_TIMEOUT on the GitHub OAuth callback, sluggish overall dev startup). Strip @sentry/nextjs, @sentry/node, @spotlightjs/spotlight, the four sentry.*.config.ts files, withSentryConfig, instrumentation.ts, the /spotlight admin page + nav entry, the SENTRY_SPOTLIGHT envs, the 8969 port mapping, and related docs/license allowlist entries. Closes #110 Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
CaseyHoover
force-pushed
the
chore/remove-sentry
branch
from
2d69968 to
5d474cf
Compare
Contributor
|
🎉 This PR is included in version 1.0.5 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
@sentry/nextjs,@sentry/node, and@spotlightjs/spotlightfrom the project entirely.withSentryConfigfromapps/web/next.config.ts, deletes the foursentry.*.config.tsfiles andinstrumentation.ts, stripsSentry.init/Sentry.captureExceptionfromapps/api/src/{index,app}.ts, and removes the/spotlightadmin page + nav entry.SENTRY_SPOTLIGHT/NEXT_PUBLIC_SENTRY_SPOTLIGHTenv defaults, the8969:8969devcontainer port, thespotlight server &invocation inpnpm dev, README/CONTRIBUTING references, and the@sentry/clilicense allowlist entry independency-review.yaml.Why
Per #110: Sentry/OpenTelemetry instrumentation caused severe dev-server slowdowns (notably a consistent 10s
UND_ERR_CONNECT_TIMEOUTon the GitHub OAuth callback diagnosed in #109). Removing it fully restored≤70mscallback latency and improved overall dev performance. Replacement observability tooling is intentionally not part of this change — see the companion investigation ticket called out in #110.Closes #110
Test plan
pnpm install—@spotlightjs/spotlightremoved, no peer warnings introducedpnpm lint— passespnpm build— web + api build clean; the/spotlightroute is gone from the route manifestpnpm test— 4 files / 20 tests passpnpm format:check— cleanpnpm dev, sign in, confirm admin sidebar no longer shows Spotlight and the GitHub OAuth callback completes quickly🤖 Generated with Claude Code