`deleteSourcemapsAfterUpload: true` does not delete .next/server/** source maps

[rodolfoBee]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

10.38.0

Framework Version

"next": "15.3.2",     "react": "^19.0.0",

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Create a nextJS app
2. Install the Sentry SDK
3. add the following to next.config.js:

sourcemaps:{
  deleteSourcemapsAfterUpload:true,
},

4. Build the app with next build

Expected Result

All sourcemaps produced by the build are deleted after upload

Actual Result

Source maps in .next/server/** are not deleted:

Additional Context

Same issue as reported here for the CSS folder: #18125

Priority

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.}

[linear]

JS-1665

[s1gr1d]

Hi, there has been an issue with this previously so the source maps are not deleted anymore on the server: #13099

The paths can explicitly be set with an array of globs in filesToDeleteAfterUpload. Make sure to enable hidden source maps (devtool = 'hidden-source-map') in case you want to delete them. Otherwise, a sourceMappingUrl comment is added to each file which will look for the source map source - and this leads to this error of not finding the source map.

[peter-knips]

@s1gr1d Thank you for the answer 😄 The Sentry docs state that the source maps are deleted to better the security, does keeping the source maps in the server folder impact the security, or is this point only relevant for the files the client loads?