-
-
Notifications
You must be signed in to change notification settings - Fork 179
UfligyJS un-necessarily pinned at the latest and buggy release #355
Comments
It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please either update the issue with the template and reopen, or open a new issue. Also we use latest version of |
@lukeapage anyway we can decrease version to |
If yes, feel free to a send PR and we release patch version |
This allows users of the plugin to pin to older versions to avoid bugs. 3.1.4 picked purely because its in the package lock file as what handlebars pins to. Fixes webpack-contrib#355
Sure, done. |
I think it must be only in peerDependencies to control it outside package |
@Delagen it is plugin, and he should use this as |
@evilebottnawi UglifyJS is very unstable at this branch, so it will broke project sometimes if version does not fix to certain revision |
@Delagen use lock files |
@evilebottnawi Thanks for this recommendation. I'll try it |
https://github.com/webpack-contrib/uglifyjs-webpack-plugin/blob/master/package.json#L50
pins uglify to 3.4.9
But there are some bad uglify-js bugs with 3.4.9:
mishoo/UglifyJS#3245
mishoo/UglifyJS#3257
mishoo/UglifyJS#3260
and now as a consumer of this plugin I cannot specify the uglify-js version in my parent package.json in order to use a non-buggy release.
The text was updated successfully, but these errors were encountered: