Duplicate of #32. See #32 (comment) for a workaround.

this is no duplicate.. the workaround doesn't work anymore

Yup this is very unfortunate. Patch version breaking stuff... :( https://travis-ci.org/Hotell/typescript-lib-starter/builds/244709499?utm_source=github_status&utm_medium=notification

It is a duplicate. The workaround doesn't work exactly as noted there anymore, but if you change uglify-js "^2.8.29" to uglify-js "^2.8.22". Everything is fine. Still an ugly workaround though.

I don't get it.

uglify-js@^2.6, uglify-js@^2.8.22, "uglify-js@git://github.com/mishoo/UglifyJS2#harmony-v2.8.22":
  version "2.8.22"
  resolved "git://github.com/mishoo/UglifyJS2#278577f3cb75e72320564805ee91be63e5f9c806"
  dependencies:
    source-map "~0.5.1"
    yargs "~3.10.0"
  optionalDependencies:
    uglify-to-browserify "~1.0.0"

...

uglifyjs-webpack-plugin@^0.4.4, uglifyjs-webpack-plugin@^0.4.6:
  version "0.4.6"
  resolved "https://registry.yarnpkg.com/uglifyjs-webpack-plugin/-/uglifyjs-webpack-plugin-0.4.6.tgz#b951f4abb6bd617e66f63eb891498e391763e309"
  dependencies:
    source-map "^0.5.6"
    uglify-js "^2.8.22"
    webpack-sources "^1.0.1"

That is the yarn.lock file. I won't say that is a workaround.

It is a workaround, because it works. This is the exact same workaround as posted in #32, with uglify-js "^2.8.22" modified from uglify-js "^2.8.29". Like I said. It's not pretty, but it works.

There was a better workaround, just run the yarn add git://github.com/mishoo/UglifyJS2#harmony-v2.8.22 --dev command. which be mentioned in readme. But the 0.4.6 version broken this. that's why I create this issue.

@pkeuter This is not about the regular versions, but about the harmony branch. If uglifyjs-webpack-plugin states regular 2.8.29 as dependency, npm doesn't care if you have the harmony branch as dependency set.

@kurtextrem I know this is about the harmony branch, but changing the yarn.lock file as mentioned before, will let this plugin use the older version of the harmony branch of UglifyJS. Again: it's not a brilliant "solution", but it fixes the build for me.

Will be fixed by #63 soon, currently ES2015 minification isn't supported directly 😞

The other question is, why is a patch version breaking things? Just by removing this line: https://github.com/webpack-contrib/uglifyjs-webpack-plugin/blob/master/package.json#L54 this whole issue would be fixed again.

@kurtextrem peerDependency broke webpack, bc of the missing uglify package, so just reverting wouldn't fix it

@kurtextrem also note that for <1.0.0, semver guarantees don't exist.