javascript - How do I turn off source maps in production in Gatsby v2? - Stack Overflow

admin管理员组

文章数量:1343161

I'm struggling how to disable source maps for production since the default Webpack set up is to leave out the devtool option, but Gatsby v2 is enabling it. I've tried ing up with a way based on the old version and the new docs, but it doesn't work:

// gatsby-node.js
exports.onCreateWebpackConfig = ({ actions, stage }) => {
  if (stage === 'build-javascript') {
    // turn off source-maps
    actions.setWebpackConfig({
      devtool: false
    })
  }
};

I'm struggling how to disable source maps for production since the default Webpack set up is to leave out the devtool option, but Gatsby v2 is enabling it. I've tried ing up with a way based on the old version and the new docs, but it doesn't work:

// gatsby-node.js
exports.onCreateWebpackConfig = ({ actions, stage }) => {
  if (stage === 'build-javascript') {
    // turn off source-maps
    actions.setWebpackConfig({
      devtool: false
    })
  }
};

• javascript
• webpack
• gatsby

Share Improve this question Follow asked Aug 21, 2018 at 17:29 SiaSia 9,23166 gold badges3232 silver badges5252 bronze badges 4

• I did just find this smart workaround - You can modify your package.json file and append "&& rm build/**/*.map" to your build mand. – Sia Commented Aug 21, 2018 at 17:42
• 1 so it looks like my solution in the question does work. either finder was not refreshing the file list or the build was not removing old sourcemap files – Sia Commented Aug 21, 2018 at 18:03
• 1 It should work — I use the same code, but without the condition. – Artem Sapegin Commented Aug 21, 2018 at 18:35
• Oh hey @ArtemSapegin! :) It does. Apparently the public folder is not deleted on each build so source maps I had previously created were still in there. – Sia Commented Aug 21, 2018 at 20:57

Add a ment  | 

2 Answers 2

Sorted by: Reset to default 6

The code in the question is the correct solution. The problem was that Gatsby does not delete the /public/ folder on each build so previously created source maps were still there. So, first delete that folder, then run the build step.

The above solution works. There is another option using gatsby plugin gatsby-plugin-no-sourcemaps

Install the plugin first

npm i gatsby-plugin-no-sourcemaps

After that goto gatsby-config.js in your project root.

Add this in plugins array

gatsby-plugin-no-sourcemaps

Goto to public folder, delete all file. Run build mand again gatsby build. Now build will not have .map files.

gatsby-config.js will look like this.

本文标签： javascriptHow do I turn off source maps in production in Gatsby v2Stack Overflow