Skip to main content

[Next.js] Why are static/chunks frames still unmapped after widenClientFileUpload?

Issue

I already set widenClientFileUpload: true and rebuilt, but some stack frames under static/chunks/ still show as minified (for example “Unminify Code”), and uploads still omit files such as framework*, polyfills*, and webpack*.

Applies To

  • All SaaS Customers and Self-Hosted Users

  • @sentry/nextjs

  • Source Maps

  • widenClientFileUpload and sourcemaps.ignore

  • Error Monitoring

Resolution

widenClientFileUpload expands which client files are eligible for upload. The SDK still skips several Next.js internal chunk patterns on purpose, because they are usually framework or dependency code, not your app code.

Those default ignore patterns include:

  • static/chunks/framework-* and static/chunks/framework.*

  • static/chunks/polyfills-*

  • static/chunks/webpack-*

  1. Confirm widenClientFileUpload: true is set in withSentryConfig. If it is not, start with Frames from static/chunks/ folder are not source mapped.

  2. If the unmapped frames are only framework*, polyfills*, or webpack*, treat that as expected. Those maps are rarely useful for debugging your application.

  3. If you are on @sentry/nextjs before 10.37.0 and you still need those maps, override the ignore list:

export default withSentryConfig(nextConfig, {
  widenClientFileUpload: true,
  sourcemaps: {
    ignore: [],
  },
});

On 10.37.0 and later, top-level sourcemaps.ignore only adds patterns. It does not clear the SDK defaults, so ignore: [] no longer uploads those internal chunks.

Did this answer your question?