Conversation
Contributor
size-limit report 📦
|
logaretm
approved these changes
Mar 16, 2026
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
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.
When
withSentryConfigis used with Next.js 16 + turbopack, the SDK auto-enablesproductionBrowserSourceMaps: trueanddeleteSourcemapsAfterUpload: true. After the build,.mapfiles are deleted, but the corresponding//# sourceMappingURL=...comments remain in the JS chunks.When browsers (e.g. Chrome DevTools) request these nonexistent
.mapfiles, Next.js 16 (turbopack) does not return a 404. Instead, the request falls through to the app router, where catch-all routes handle it. Since middleware matchers typically exclude_nextpaths, middleware does not run forthese requests, causing SSR failures for middleware-dependent features (e.g. Clerk's
auth()throws becauseclerkMiddleware()headers are absent).This fix strips dangling
sourceMappingURLcomments from client JS/CSS files after source map deletion, but only for turbopack builds where the issue manifests.deleteArtifacts()in the post-build hookstatic/closes #19600