[nextjs] Add option to suppress "could not determine source map reference" warnings for specific files

[skinnymanmusic]

Problem

When using @sentry/nextjs with Next.js 16 and Turbopack, the Source Map Upload Report produces many warnings for files that legitimately don't have source maps:

- warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/app/page_client-reference-manifest.js)
- warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/interception-route-rewrite-manifest.js)
- warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/middleware-build-manifest.js)
- warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/next-font-manifest.js)
- warning: could not determine a source map reference (Could not auto-detect referenced sourcemap for ~/server-reference-manifest.js)

These files are auto-generated Next.js/Turbopack internals that:

1. Don't have source maps (by design)
2. Don't contain user code worth debugging
3. Create significant noise in CI logs (100+ warnings for larger apps)

Current Workarounds

• silent: true - Suppresses ALL logs, including useful upload success/failure info
• sourcemaps.ignore - Only prevents upload, doesn't suppress the warning

Neither provides the desired behavior: suppress warnings for expected missing source maps while keeping visibility into actual upload issues.

Proposed Solution

Add a new option like:

withSentryConfig(nextConfig, {
  sourcemaps: {
    // Suppress warnings for files matching these patterns
    suppressMissingWarnings: [
      '**/*_client-reference-manifest.js',
      '**/*-manifest.js',
    ],
  },
})

Or alternatively, a simpler boolean:

withSentryConfig(nextConfig, {
  sourcemaps: {
    // Don't warn about files without source maps
    warnOnMissing: false,
  },
})

Environment

• @sentry/nextjs: 10.x (latest)
• Next.js: 16.1.1
• Build: Turbopack (default in Next.js 16)
• pnpm monorepo

Additional Context

These warnings mask real issues in CI logs. When there's an actual source map problem, it's buried in 100+ expected warnings. This defeats the purpose of having verbose logs for debugging.

[linear]

JS-1501

[chargome]

Hey @skinnymanmusic thanks for reaching out. Sounds reasonable we could provide a default set of files that should emit warnings and additionally add a pattern matcher.

[skinnymanmusic]

Yes please. 🙏 What's the Plan? Contact: 231.335.SKNY Booking: DJ Skinny ***@***.***> Website: <http://www.skinnymanmusic.com/>

…

On Mon, Jan 19, 2026 at 03:23 Charly Gomez ***@***.***> wrote: *chargome* left a comment (getsentry/sentry-javascript#18872) <#18872 (comment)> Hey @skinnymanmusic <https://github.com/skinnymanmusic> thanks for reaching out. Sounds reasonable we could provide a default set of files that should emit warnings and additionally add a pattern matcher. — Reply to this email directly, view it on GitHub <#18872 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APNTSAAKJ6MQ7JACAX53X5L4HSIBLAVCNFSM6AAAAACSCDQEKGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONRXGA2DMNZVGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[chargome]

I'll pick this issue up, you'll be notified once this is released