[sentry-junior]

Part of CLI-1FN. About 88% of sampled events are the zero-pairs error, and nearly all of them are @sentry/nextjs uploading .next/static/chunks, .next/static/immutable/chunks, or .next/server. The hint only named Vite and webpack settings, and neither applies to Next.js. This PR makes the hint match the build output. The error still fires as before.

The "JS and maps, but no pairs" message also blamed basenames. Pairing also follows sourceMappingURL comments, so it now says what actually failed.

Before

$ sentry sourcemap upload .next/static/chunks
Error: Found 7 JS file(s) in '.next/static/chunks' but no companion .map files. Your bundler is not emitting sourcemaps. For Vite/Astro: `vite.environments.client.build.sourcemap: 'hidden'`. For webpack: `devtool: 'hidden-source-map'`. Pass --allow-empty to suppress.

$ sentry sourcemap upload .next/static/chunks   # 7 JS + 1 unrelated .map
Error: Found 7 JS and 1 .map file(s) in '.next/static/chunks' but no JS file has a matching `<name>.map` companion. Check that your bundler emits JS and sourcemaps with matching basenames. Pass --allow-empty to suppress.

$ sentry sourcemap upload .next/server
Error: Found 7 JS file(s) in '.next/server' but no companion .map files. Your bundler is not emitting sourcemaps. For Vite/Astro: `vite.environments.client.build.sourcemap: 'hidden'`. For webpack: `devtool: 'hidden-source-map'`. Pass --allow-empty to suppress.

After

$ sentry sourcemap upload .next/static/chunks
Error: Found 7 JS file(s) in '.next/static/chunks' but no companion .map files. Your bundler is not emitting sourcemaps. For Next.js, remove `productionBrowserSourceMaps: false` from next.config (`withSentryConfig` turns it on), or set `sourcemaps.disable: true` in `withSentryConfig` to skip the upload. Pass --allow-empty to suppress.

$ sentry sourcemap upload .next/static/chunks   # 7 JS + 1 unrelated .map
Error: Found 7 JS and 1 .map file(s) in '.next/static/chunks' but no JS file has a sourcemap: none has a sibling `<name>.map` or a `//# sourceMappingURL=` comment pointing at a map in this directory. For Next.js, remove `productionBrowserSourceMaps: false` from next.config (`withSentryConfig` turns it on), or set `sourcemaps.disable: true` in `withSentryConfig` to skip the upload. Pass --allow-empty to suppress.

$ sentry sourcemap upload .next/server
Error: Found 7 JS file(s) in '.next/server' but no companion .map files. Your bundler is not emitting sourcemaps. For Next.js server output, check that next.config does not turn server sourcemaps off, e.g. a custom `webpack()` that sets `config.devtool`, or `experimental.serverSourceMaps: false`. Pass --allow-empty to suppress.

The first case comes from a real Next.js 16 Turbopack build with productionBrowserSourceMaps: false. That is the only setup I could reproduce that leaves .next/static with zero maps under withSentryConfig. Rebuilds into an existing .next, or with only .next/cache restored, re-emit the maps. Non-Next paths keep the Vite and webpack hint.

via bete.

--

View Session [Sentry]

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated
sentry-local	Skipped		Nov 4, 2026 9:47am UTC

[BYK]

I mean at this point why not also offer to fix this for them?