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.
By sacrificing a small amount of source map accuracy, we make incremental development builds about 20% faster.
Learn about the different modes here: https://webpack.js.org/configuration/devtool/#devtool
About the trade-off
Say you have code like this:
With
source-maps
, DevTools will allow you to step through each operation within that line: first, thefoo
assignment, then thebar
assignment, then thebaz
assignment.With
cheap-module-eval-source-map
, DevTools will only allow you to break at that entire line.In my experience, it’s not worth the performance penalty.
And besides, if one needs to step through things more granularly, they can temporarily change their Webpack settings and rebuild.