[web] Do not delete source map from production build #779
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
In the context of https://trello.com/c/hInThumV (internal link), we realized that source maps are missing in the production build.
They would have been useful for debugging the error we were facing. In fact, there is a Webpack recommendation about serving source maps in production too
The weird thing is that we already had the
devtool
webpack option set to"source-map"
, the value recommended for production builds. But, surprisingly, files were not there.After closely checking the webpack configuration file, the culprit came to scene: the
deleteOriginalAssets
option of theCompressionWebpackPlugin
. It was set astrue
and it does not honor the pattern given intest
option.Solution
Fortunately, it's something that was fixed long time ago. For us is just about switching from
true
to"keep-source-map"
value.Tests
Tested manually by checking the dist/ content after running the
NODE_ENV=production npm run build
command.Click to show/hide ls -l dist/ output BEFORE the change
Click to show/hide ls -l dist/ output AFTER the change