webpack: throwing an error if I disable source map in uglifyjs plugin

I think this is a more appropriate location to file this issue: https://github.com/webpack/extract-text-webpack-plugin/issues/98

I disabled extract text plugin and it still gives an error. Its probably in webpack.

So just re posting this:

I get an error if I turn off source map in

new webpack.optimize.UglifyJsPlugin({
    compress: {
        warnings: false
    }
    , sourceMap: false
  })

I’m trying to disable source map since my build takes 5 minutes long. Removing it yields 1 minute 40 seconds.

Here’s part of my stack trace

ERROR in bundle.js from UglifyJs
TypeError: Cannot read property 'sections' of null
    at new SourceMapConsumer (/var/www/project/node_modules/webpack/node_modules/webpack-core/node_modules/source-map/lib/source-map/source-map-consumer.js:24:21)
    at /var/www/project/node_modules/webpack/lib/optimize/UglifyJsPlugin.js:62:23
    at Array.forEach (native)
    at Tapable.<anonymous> (/var/www/project/node_modules/webpack/lib/optimize/UglifyJsPlugin.js:44:10)
    at Tapable.next (/var/www/project/node_modules/webpack/node_modules/tapable/lib/Tapable.js:69:14)
    at Tapable.<anonymous> (/var/www/project/node_modules/webpack/lib/optimize/UglifyJsPlugin.js:136:4)
    at Tapable.applyPluginsAsync (/var/www/project/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Tapable.<anonymous> (/var/www/project/node_modules/webpack/lib/Compilation.js:564:9)
    at Tapable.next (/var/www/project/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at ExtractTextPlugin.<anonymous> (/var/www/project/node_modules/extract-text-webpack-plugin/index.js:303:4)
    at Tapable.applyPluginsAsync (/var/www/project/node_modules/webpack/node_modules/tapable/lib/Tapable.js:71:13)
    at Tapable.<anonymous> (/var/www/project/node_modules/webpack/lib/Compilation.js:560:8)
    at Tapable.next (/var/www/project/node_modules/webpack/node_modules/tapable/lib/Tapable.js:67:11)
    at ExtractTextPlugin.<anonymous> (/var/www/project/node_modules/extract-text-webpack-plugin/index.js:279:5)
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:52:16
    at done (/var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:248:21)
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:44:16
    at /var/www/project/node_modules/extract-text-webpack-plugin/index.js:270:6
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:52:16
    at done (/var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:248:21)
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:44:16
    at /var/www/project/node_modules/extract-text-webpack-plugin/index.js:267:13
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:187:20
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:239:13
    at _arrayEach (/var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:91:13)
    at _each (/var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:82:13)
    at Object.async.forEachOf.async.eachOf (/var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:238:9)
    at Object.async.forEach.async.each (/var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:215:22)
    at /var/www/project/node_modules/extract-text-webpack-plugin/index.js:241:11
    at /var/www/project/node_modules/extract-text-webpack-plugin/node_modules/async/lib/async.js:187:20

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 26
  • Comments: 35 (4 by maintainers)

Commits related to this issue

Most upvoted comments

when using new UglifyJsPlugin and --opimize-minimize (or -p) you are adding the UglifyJsPlugin twice. Omit the CLI option.

+960
sokra on Nov 30, 2015

try to reinstall all dependencies.

+138
sokra on Aug 26, 2015

@sokra just tried reinstalling dependencies. Still getting the same error on build:

ERROR in bundle.js from UglifyJs
TypeError: Cannot read property 'sections' of null
    at new SourceMapConsumer
+31
chiefjester on Aug 27, 2015

With Webpack 4, mode: 'production' will automatically add optimizations plugins.

If you get the following warning/error message when building with mode: 'production', try fixing by below instruction.

TypeError: Cannot read property 'sections' of null 👉 Remove `new UglifyJsPlugin` from plugins part
schema id ignored LoaderOptionsPlugin              👉 Remove `new LoaderOptionsPlugin` plugin from config
schema id ignored SourceMapDevToolPlugin           👉 Remove `devtool` config
+15
ReeganExE on Feb 26, 2018

+1 fix by remove -p

+13
luoyjx on Mar 15, 2017

Is there a fix coming for this? In my opinion Webpack should be smart enough to omit one or the other f both are present.

+9
isaacrlevin on Jun 2, 2017

+1 fix by remove -p

+8
deot on Mar 27, 2017

Have similar issue, but i don’t specify sourceMap: false. Only when i declare this, build pass.

+8
Intey on May 2, 2016

Thanks so much @sokra, This helped me!

+8
sinaler on Dec 17, 2015

@damianobarbati, you might pass it as minimizer option rather than push it as plugin part.

const configs = {
  mode: "production",
  entry: "./index",
  output: {
    filename: "bundle.js"
  },
  optimization: {
    minimize: true,
    minimizer: [
      new UglifyJsPlugin({
        sourceMap: true,
        uglifyOptions: {
          // ...
        }
      })
    ]
  }
};
+7
ReeganExE on Feb 26, 2018

@sokra removing -p does indeed fixes it for me. Is this intended behavior though? if a flag in cli does the same thing in config, it will just apply it twice?

I’ll gladly make a PR if you can just give me pointers where to look. Let me know if we don’t plan to fix this, and I’ll have this close.

+6
chiefjester on Nov 27, 2016

I am getting the same error here when using sourcemap false and --optimize-minimize (if I leave the optimize out it works).

+6
angelomichel on Sep 4, 2015

do not remove UglifyJsPlugin, just add sourceMap: true to its config

+4
skogtake on Feb 26, 2018

@sokra I’ve setup a sample repo to reproduce the bug: https://github.com/deezahyn/webpack-production-test

+4
chiefjester on Aug 27, 2015

Another way I was able to get rid of this issue was by removing devtool: 'source-map' from webpack config.

+3
pardoman on Aug 1, 2018

What’s your devtool?

+3
SimenB on Aug 24, 2015

when using yarn, you could add this to your package.json file:

"resolutions": {
    "webpack/uglifyjs-webpack-plugin": "^1.1.8"
  },

this will replace webpack original dependency with a more recent one, so you could still use -p switch.

+1
roeycohen on Feb 12, 2018

Thanks @sokra it also fixed it for me as well

+1
jquintozamora on Nov 20, 2016

Thanks @sokra, you fixed this bug for me too 😃

+1
Zjaaspoer on May 22, 2016

Thanks @sokra it also fixed it for me

+1
guzmonne on Apr 21, 2016

same error

+1
hanai on Nov 26, 2015
Read more comments on GitHub
← webpack: There is another module with an equal name when case is ignored.
webpack: Tree shaking completely broken? →