fix(webpack-plugin): delete CSS sourcemaps after upload#3962
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
marandaneto
commented
Jun 25, 2026
Contributor
|
Reviews (1): Last reviewed commit: "chore: update changeset scope" | Re-trigger Greptile |
Member
Author
|
follow up #3949 (comment) |
Contributor
|
Reviews (2): Last reviewed commit: "test: parameterize css sourcemap cleanup..." | Re-trigger Greptile |
Contributor
Contributor
|
Size Change: +280 B (0%) Total Size: 16.9 MB
ℹ️ View Unchanged
|
ioannisj
approved these changes
Jun 25, 2026
ioannisj
left a comment
Contributor
There was a problem hiding this comment.
Approved but letft a couple of comments
Contributor
|
Reviews (3): Last reviewed commit: "fix: handle css sourcemap cleanup failur..." | Re-trigger Greptile |
This was referenced Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
@posthog/nextjs-configusers with SCSS/CSS source maps can still end up with.next/static/css/**/*.css.mapfiles in production output after source map upload. We should remove those maps whendeleteAfterUploadis enabled, but not upload CSS assets to PostHog since error tracking does not process them.Fixes #2383
Partially addresses #2527 by deleting browser CSS sourcemaps from webpack output when
deleteAfterUploadis enabled.Changes
deleteAfterUploadis enabled.@posthog/webpack-plugin, since no@posthog/nextjs-configsource changed.Release info Sub-libraries affected
Libraries affected
Checklist
If releasing new changes
pnpm changesetto generate a changeset file🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Implemented with pi in a dedicated worktree. The approach follows reviewer guidance from #3949: CSS source maps are deleted when
deleteAfterUploadis enabled, without adding CSS assets to sourcemap upload processing.Validation run: