Sourcemaps about react-webpack-rails HOT 3 CLOSED

I'm not familiar with Sentry source maps. Why not just use Webpack's built-in source maps?

https://webpack.github.io/docs/configuration.html#devtool

from react-webpack-rails.

My sourcemaps are emitted by Webpack just fine. My issue is with providing them to Sentry. Sentry offers two ways :

• making them publicly available (discouraged)
• publishing them to their server as part of deployment

The second option I find difficult, because I don't really understand the deployment flow and how to add a step to publish the source maps to Sentry (I'm using Heroku and the deployment guide you provided)

The first option is the one I tried. I therefore added the SourceMapDevToolPlugin in my production.config.js file :

const Webpack = require('webpack');
const config = require('./../webpack.config');

config.plugins.push(
  new Webpack.DefinePlugin({'process.env': {'NODE_ENV': '"production"'}}),
  new Webpack.SourceMapDevToolPlugin({
    filename: '../../../public/assets/javascripts/react_bundle.map.js'
  })
);

module.exports = config;

This is fine, my sourcemap file ends up in the public directory, ready to be served to Sentry. But the soucemap comment at the end of my file reads:

// # sourceMappingURL=../../../public/assets/javascripts/react_bundle.map.js

And I don't know how to make it read :

// # sourceMappingURL=/assets/javascripts/react_bundle.map.js

Both options suggested by Sentry have proven a dead end for me, and I was wondering if you had any advice on the correct way to go :) Thanks !

from react-webpack-rails.

Wait ... I'm in the wrong repo. I meant to publish in react_webpack_rails. So sorry ! Closing this.

from react-webpack-rails.