fix: migrate Sentry configuration to Next.js 15 App Router #13
Conversation
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
Resolves critical build failure caused by outdated Sentry configuration incompatible with Next.js 15 App Router. Changes: - Created src/instrumentation.ts for server-side Sentry initialization - Created src/instrumentation-client.ts for client-side initialization - Added src/app/global-error.tsx to handle React rendering errors - Added src/app/not-found.tsx for custom 404 page - Removed deprecated sentry.*.config.ts files - Updated Sentry packages to v10.16.0 - Removed old Sentry import from layout.tsx Technical Details: - Sentry's withSentryConfig wrapper temporarily disabled due to Next.js 15 compatibility issue (generates Pages Router error pages incompatible with App Router) - Implemented manual instrumentation hooks following Next.js App Router patterns - Added onRequestError and onRouterTransitionStart exports - Build now succeeds with proper NODE_ENV=production Testing: - ✅ Production build passes (yarn build:ci) - ✅ All 254 tests passing - ✅ TypeScript compilation successful -⚠️ ESLint warning in useMartianTime.ts (pre-existing, tracked separately) References: - https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/ - getsentry/sentry-javascript#14526
Remove the old sentry.*.config.ts files that are no longer needed after migrating to Next.js 15 App Router instrumentation pattern. These files have been replaced by: - src/instrumentation.ts (server-side) - src/instrumentation-client.ts (client-side)
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
Resolves critical build failure caused by outdated Sentry configuration incompatible with Next.js 15 App Router.
Problem
Build was failing with:
Root Cause: Deprecated Sentry config files using Pages Router patterns incompatible with App Router.
Changes
New Files
src/instrumentation.ts- Server-side Sentry initializationsrc/instrumentation-client.ts- Client-side Sentry initializationsrc/app/global-error.tsx- Custom global error handlersrc/app/not-found.tsx- Custom 404 pageModified Files
src/app/layout.tsx- Removed old Sentry importnext.config.ts- Temporarily disabledwithSentryConfigwrapper (documented)package.json- Updated Sentry to v10.16.0Removed Files
sentry.client.config.ts(deprecated)sentry.server.config.ts(deprecated)sentry.edge.config.ts(deprecated)Technical Details
onRequestErrorandonRouterTransitionStartexportsTesting
yarn build:ciNote on Sentry Wrapper
The
withSentryConfigwrapper is temporarily disabled due to a known issue where Sentry v10 generates Pages Router error pages incompatible with Next.js 15 App Router. The instrumentation files work correctly for error tracking; only the build-time wrapper needs to be re-enabled once Sentry releases a fix.Tracking: getsentry/sentry-javascript#14526
References