Source maps uploaded to error tracking service

Minified production JavaScript produces stack traces like a.b is not a function at t (main.abc123.js:1:4821) — unactionable without the corresponding source map. When source maps are not uploaded to the error tracking service, every production stack trace requires a manual deobfuscation step that most teams skip, leaving errors effectively uninvestigated. ISO 25010 reliability.fault-tolerance depends on diagnostic capability; without readable stack traces, fault isolation time increases dramatically. Exposing source maps publicly (via productionBrowserSourceMaps: true) solves the readability problem but exposes your full source code to anyone with DevTools.

Upload source maps to your error tracking service during the build — never serve them publicly. With Next.js and Sentry, withSentryConfig handles the upload automatically.

// next.config.ts
import { withSentryConfig } from '@sentry/nextjs'

export default withSentryConfig(
  { /* your next config */ },
  {
    org: process.env.SENTRY_ORG,
    project: process.env.SENTRY_PROJECT,
    // Source maps uploaded to Sentry, not served publicly:
    sourcemaps: { disable: false },
  }
)

Verify by triggering a deliberate error in staging and confirming the Sentry stack trace shows original filenames and line numbers, not minified identifiers.