Skip to content

Wrong devtool type at Production>Source Mapping guide #1567

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 3, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/content/guides/production.md
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,7 @@ If you decide to try another, just make sure your new choice also drops dead cod

## Source Mapping

We encourage you to have source maps enabled in production, as they are useful for debugging as well as running benchmark tests. That said, you should choose one with a fairly quick build speed that's recommended for production use (see [`devtool`](/configuration/devtool)). For this guide, we'll use the `cheap-module-source-map` option in _production_ as opposed to the `inline-source-map` we used in _development_:
We encourage you to have source maps enabled in production, as they are useful for debugging as well as running benchmark tests. That said, you should choose one with a fairly quick build speed that's recommended for production use (see [`devtool`](/configuration/devtool)). For this guide, we'll use the `source-map` option in _production_ as opposed to the `inline-source-map` we used in _development_:

__webpack.prod.js__

Expand All @@ -165,7 +165,7 @@ __webpack.prod.js__
const common = require('./webpack.common.js');

module.exports = merge(common, {
+ devtool: 'cheap-module-source-map',
+ devtool: 'source-map',
plugins: [
new UglifyJSPlugin()
]
Expand Down