UglifyJS errors don't bail the build with --bail

[graingert]

webpack --bail:

ERROR in entrypoint-xxx.bundle.js from UglifyJs
Unexpected character '`' ./src/path/to/file.js:1487,0]

[bebraw]

Can you provide a test case so this can be debugged?

[pdillon]

@bebraw Check out at https://github.com/pdillon/webpack-bail-example. Ran into this issue where the babel loader was pulling in files outside of the include path, bypassing transpilation, and uglify throws an error.

[bebraw]

@pdillon Thanks. I added this to webpack 2 work. Given there's a test case, it should be easier to figure out the root cause.

[pdillon]

@bebraw would it make sense for bail to map to the NoErrorsPlugin, and for the plugin to pass an error to the callback if compilation.errors > 0?

[bebraw]

@pdillon I'm not sure. I think we'll have to wait for Tobias to check this out to get the behavior right.

[gdborton]

Is this not going to be fixed in webpack 1.13.x?

[JLHwung]

Here is another minimal example.

Webpack 2 does not bail when babel finds a syntax error.

[q42jaap]

I've created a workaround that will detect UglifyJs errors and exit the process with a non-zero status code:

class DetectUglifyJsErrors {
  apply(compiler) {
    compiler.plugin('compilation', compilation => {
      compilation.plugin('optimize-chunk-assets', (chunks, callback) => {
        if (compilation.errors.length > 0) {
          compilation.errors.forEach(error => {
            console.error(`ERROR in ${error.message}`);
          });
          process.exit(1);
        }
        callback();
      });
    });
  }
}

This works for me and outputs the same message webpack would otherwise output.

[webpack-bot]

This issue had no activity for at least half a year.

It's subject to automatic issue closing if there is no activity in the next 15 days.

[webpack-bot]

Issue was closed because of inactivity.

If you think this is still a valid issue, please file a new issue with additional information.