Razzle: Disable SourceMaps in production

[Ronny25]

Is there any way to disable generating of SourceMaps for production build?

CRA has .env variable called - GENERATE_SOURCEMAP.

I cannot see anything in docs. So, I suppose, the only possible way is to extend webpack config inside razzle.config.js?

[krazyjakee]

extend webpack config inside razzle.config.js

This is the solution. An example razzle.config.js.

module.exports = {
  modify: (config, { target, dev }) => {
    config.devtool = dev ? 'source-map' : false;
    return config;
  },
};

[Ronny25]

@krazyjakee yes that what I was talking about and I have the same in my code right now.
But this is a bit overcomplicated as for me to achieve such a goal. Not too accurate, to be honest.
Prefer the CRA way to do it.
However, if it is the only possible way then ok.

[krazyjakee]

@Ronny25 If you really want to use environment variables you could do something like:

module.exports = {
  modify: config => {
    config.devtool = process.env.GENERATE_SOURCEMAP ? 'source-map' : false;
    return config;
  },
};

Then you get the same accuracy as CRA.

[Ronny25]

@krazyjakee that's not completely true 😄
Firstly, you need to create a config file with some logic inside then an env variable, sounds strange 😉
But I can live with is 😁

[SamirJouni]

@krazyjakee
This only seems to disable source maps for .js files.
.css files still get source map files generated.