Disable source maps in production (v2) #3818
Conversation
KyleAMathews
left a comment
KyleAMathews
left a comment
There was a problem hiding this comment.
Thanks for jumping on this!
| // sure that your web server restricts access to them (e.g. with | ||
| // basic auth): | ||
| // | ||
| // exports.modifyWebpackConfig = ({ config, stage }) => { |
There was a problem hiding this comment.
The API for modifying webpack config has changed. Instead of directly mutating the webpack config, there's a new action named setWebpackConfig. If you grep the v2 branch, you'll find a number of usages for this + I think there's docs already.
tomazy
changed the title
|
Hmmmm... so I might have changed my mind about this. I agree with @jquense (#3817 (comment)) that they're more useful than not. Instead of disabling it by default — how about instead we a) investigate using relative paths, removing comments and otherwise making them more tidy by default and b) add a plugin to easily disable producing source maps by modifying the webpack config which also conveniently would speed up builds some. |
2 participants
Fixes #3817