how to generate sourceMaps for production mode? about yarsk

[bradleyboy]

Open conf/webpack.production.js and change it to:

module.exports = require('./make-webpack-config')({
  production: true,
  devtool: 'source-map'
});

Then when you build, sourcemaps will be generated for both CSS and JS.

[zaggino]

thanks a lot, commented out line in code could be also useful for others... i've just started exploring devpack coming from browserify :) i've gone through a few starters but yours is the first one not overcomplicating things (except the most basic one)

[tshddx]

Is this supposed to generate maps with the actual ES6 code, before transpilation? It doesn't seem to have any effect for me. With or without the source-map options, I can still see all my index.jsx files in the Chrome Sources tab, but they are post-transpilation.

[bradleyboy]

@BadDox Is this in production or development? In development, eval is used, which will show the sourcemap post-transpilation. You can change that by editing the devtool setting in conf/webpack.config.js:

module.exports = require('./make-webpack-config')({
  devtool: 'eval-source-map',
});

Keep in mind that the compilation and rebuilds will be slightly slower with that setting. More on the devtool options can be found in the webpack docs.

[tshddx]

Indeed, that was my issue in development.