Repository navigation
deleteSourcemapsAfterUpload: true does not delete CSS source maps #18125
Description
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.23.0
Framework Version
Next 16.0.1
Link to Sentry event
No response
Reproduction Example/SDK Setup
https://github.com/mizdra/repro-sentry-nextjs-css-source-map
The contents of next.config.ts are as follows:
import {withSentryConfig} from "@sentry/nextjs";
import type { NextConfig } from "next";
const nextConfig: NextConfig = {
/* config options here */
};
export default withSentryConfig(nextConfig, {
silent: true,
widenClientFileUpload: true,
sourcemaps: {
deleteSourcemapsAfterUpload: true,
},
disableLogger: true,
});Steps to Reproduce
$ npm i
$ npm run build
$ find .next/static -name "*.map"Expected Result
The find command returns nothing.
Actual Result
The find command returns the Source Map for .css.
$ find .next/static -name "*.map"
.next/static/chunks/76bb3875a8d326ec.css.mapAdditional Context
The source maps for *.js have been deleted, but the source maps for *.css have not been deleted.
Metadata
Metadata
Assignees
Projects
- Status
Activity
linear commentedon Nov 9, 2025
JS-1130
mizdra commentedon Nov 10, 2025
Could this be expected behavior rather than a bug? Since CSS source maps aren't uploaded to Sentry, is the deletion skipped?
mizdra commentedon Nov 10, 2025
Even if that is the expected behavior, I think many users will be confused. To prevent the original CSS code from being leaked, we must run
rm -rf .next/static/**/*.css.map. However, I don't think many people will realize they need to do that.chargome commentedon Nov 10, 2025
Hey @mizdra thanks for reporting this. We indeed to not delete these maps, we only look for any sort of js files. I agree with you that a more sensible default would be to also delete map files for css. We'll update that!
fix(nextjs): Delete css map files (getsentry#18131)
mizdra commentedon Nov 10, 2025
Thanks for fixing it so quickly!
github-actions commentedon Nov 10, 2025
A PR closing this issue has just been released 🚀
This issue was referenced by PR #18131, which was included in the 10.24.0 release.