Implement Sentry error monitoring with PII protection#117
Merged
Conversation
mostafazh
force-pushed
the
sentry-dsn-setup
branch
from
5604c09 to
8c4b21b
Compare
added 2 commits
June 23, 2026 02:22
… filtering - Set up @sentry/nextjs for client, server, and edge runtimes. - Disable user info and request/response body collection via dataCollection. - Tag events with NODE_ENV and drop non-production errors before they reach the production Sentry project. - Remove Vercel-specific assumptions (no VERCEL_ENV, no Vercel Cron Monitors instrumentation).
Move plugin:@typescript-eslint/recommended into an override for *.ts and *.tsx so that JavaScript config files like next.config.js are not checked by TypeScript-specific rules such as no-var-requires.
mostafazh
force-pushed
the
sentry-dsn-setup
branch
from
8c4b21b to
bd55dee
Compare
- Add .git-hooks/pre-push that runs npm run lint before each push. - Add prepare script to package.json so npm install sets core.hooksPath to .git-hooks for every clone. - Bypass with git push --no-verify when needed.
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.
This pull request introduces Sentry error monitoring to the project, with careful configuration to protect user privacy and to avoid collecting data in non-production environments. Sentry is set up for the client, server, and edge runtimes, and a global error handler is added to capture and report exceptions. The integration is designed to avoid collecting user information and to limit data collection to production only.
Sentry Integration and Configuration:
@sentry/nextjsas a dependency inpackage.jsonto enable Sentry error tracking.sentry.client.config.ts), server (sentry.server.config.ts), and edge (sentry.edge.config.ts) environments, each configured to:Error Handling:
src/app/global-error.tsxthat captures exceptions with Sentry and renders a generic error page using Next.js's default error component.src/instrumentation.tsto dynamically import the appropriate Sentry config based on runtime and export Sentry's request error capture function.