Repository navigation
Conversation
devtool: 'cheap-module-source-map' registers its own SourceMapDevToolPlugin, and the config also adds one explicitly with filename '[file].map'. Both write main.js.map (and every chunk's .map) with different content. webpack 5.107 let the second write win silently; 5.108+ reports it as an asset conflict and fails the build, which is why every webpack update since has had red CI. Turn off devtool and carry its options (line-only mappings to original module source) onto the explicit plugin, so the emitted maps match what shipped.
This branch has not been deployed
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
1 participant
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.
Resolves
Proposed Changes
Turn off
devtoolinwebpack.makeConfig.jsand move its options (columns: false,module: true) onto the explicitSourceMapDevToolPluginthat the config already adds.Reason for Changes
devtool: 'cheap-module-source-map'registers its ownSourceMapDevToolPlugin, so each bundle's.mapfile was emitted twice with different content. webpack 5.107 let the second write win silently. 5.108+ reports it asConflict: Multiple assets emit different content to the same filename main.js.mapand fails the build, which is why the webpack update PR has been red since May.Test Coverage
npm run compilesucceeds on the pinned webpack 5.107.0 and on 5.111.1 (installed temporarily with--no-save).main.js.mapandrenderer.js.maplistwebpack:///./src/...entries withsourcesContent.npm test(lint) is clean.