Relative to other plugins, it has a disproportionate number of dependencies. Additionally, with the advent of babili
, uglify
is no longer a necessary part of a production build process.
2 thoughts on “Consider moving `UglifyJsPlugin` out of main package.”
Comments are closed.
@wtgtybhertgeghgtwtg FWIW, I have found a rather simple solution
https://www.npmjs.com/package/babili-webpack-plugin
@jpollard-cs Yeah, my current thinking is that the package should treat Uglify as a peer dependency. Then you can decide whether to use the stable version or something else without having to fork anything.